create-issue
Create a new issue in a GitHub repository
What this skill does
# Create GitHub Issue ## Name github:create-issue - Create a new issue in a GitHub repository ## Synopsis ``` /create-issue [arguments] ``` ## Description Create a new issue in a GitHub repository ## Implementation Create a new issue in a GitHub repository with title, body, and labels. ## Usage ``` /create-issue [owner/repo] ``` This command helps you create a well-structured GitHub issue. ## What This Command Does 1. Asks for the repository (owner/repo format) 2. Prompts for issue title 3. Requests issue body/description 4. Asks for labels (optional) 5. Creates the issue using the GitHub MCP `create_issue` tool 6. Returns the issue number and URL ## Prerequisites - GitHub MCP server must be installed and configured - You must have permission to create issues in the target repository - OAuth authentication must be completed ## Example Interaction ``` User: /create-issue Claude: I'll help you create a GitHub issue. What repository? (owner/repo format) User: my-org/my-repo Claude: What should the issue title be? User: Fix memory leak in image processor Claude: Please provide a description for the issue: User: Memory usage increases continuously when processing large images. After processing 100+ images, the application crashes due to OOM errors. ## Steps to reproduce 1. Start the image processor 2. Process 100+ large images (>5MB each) 3. Observe memory usage climbing Claude: Any labels to add? (comma-separated, or press Enter to skip): User: bug, high-priority Claude: Creating issue in my-org/my-repo... Issue created successfully! #42 - Fix memory leak in image processor https://github.com/my-org/my-repo/issues/42 ``` ## Tips - Use `owner/repo` format for repository identification - Write clear, actionable issue titles - Include reproduction steps in the description - Use GitHub-flavored Markdown in descriptions - Reference related issues with `#123` syntax - Mention users with `@username` for notifications ## Related Commands - `/search-code`: Find related code before filing - `/create-pr`: Create a pull request to fix the issue - `/review-pr`: Review existing PRs related to the issue
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.