create-issue
Create a GitHub issue with title and description (auto-assigned)
What this skill does
## Language Conventions **Infer language style from the project:** - Analyze existing issues, documentation, and commit messages to detect the project's language variant (US English, UK English, etc.) - Match the spelling conventions found in the project (e.g., "initialize" vs "initialise", "behavior" vs "behaviour") - Maintain consistency with the project's established language style throughout issue titles and descriptions --- Create a GitHub issue with the following workflow: 1. Check if we're in a GitHub repository and get owner/repo info 2. **Check for organization issue types:** - Use `github/list_issue_types` MCP tool with the repository owner - If issue types exist, select the most appropriate type based on the issue context (e.g., "Bug", "Feature", "Task") - Note: This will fail for user-owned repositories (not organizations) - this is expected, proceed without issue type 3. **Check for ISSUE_TEMPLATE format:** - Look for issue templates in `.github/ISSUE_TEMPLATE/` or `.github/` directories - If templates exist, use the most appropriate template format (bug report, feature request, etc.) - Parse template structure and fill in the required sections 4. **If no ISSUE_TEMPLATE exists, use custom format:** - Infer issue title from user's request context - Generate appropriate issue description based on the context 5. **Get current user for assignment:** - Use `github/get_me` MCP tool to get the current authenticated user's login 6. **Create issue using `github/issue_write` MCP tool:** - Set `method: "create"` - Include `owner`, `repo`, `title`, `body` - Include `type` parameter if organization issue types are available (from step 2) - Include `assignees` array with current user's login for self-assignment - If assignment fails (user not a collaborator), the issue will still be created without assignment 7. Optionally add existing labels or milestone (only use labels that already exist in the repository) - Additional assignees can be added to the `assignees` array For the issue title: - Use natural, descriptive language (NOT conventional commits format like "feat:", "fix:", "chore:") - Make it clear and specific to the problem or feature - Keep it concise but informative For the issue description (when using custom format): - Include clear problem statement or feature request - Add steps to reproduce (if bug report) - Keep it structured and actionable For ISSUE_TEMPLATE format: - Follow the exact template structure and required fields - Fill in template placeholders with relevant information from user context - Maintain template formatting and sections
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.