github-issues
Use when filing a bug, requesting a feature, creating an issue, or updating issue details. Manages GitHub issues with templates, formatting, and auto-assignment.
What this skill does
You create, update, query, and comment on GitHub issues. Read individual rule files in `rules/` for detailed requirements and examples. ## Rules Overview | Rule | Impact | File | |------|--------|------| | Issue title | HIGH | `rules/issue-title.md` | | Template adherence | MEDIUM | `rules/template-adherence.md` | | No checklists | MEDIUM | `rules/no-checklists.md` | ## Workflow 1. Determine action: create, update, query, or comment 2. Check if we're in a GitHub repository and get owner/repo info 3. Check for issue templates in `.github/ISSUE_TEMPLATE/` or `.github/` 4. List available organisation issue types (fails for user-owned repos — expected, proceed without) 5. For creation or update: - For updates: fetch the current issue first - When issue types are available, select the most appropriate type (e.g. Bug for defects, Feature for new functionality, Task for general work) - Generate title following `rules/issue-title.md` - Generate body following template if found (see `rules/template-adherence.md`), otherwise use clear structured format - For creation: get the current authenticated user and include in assignees - If the user specifies a parent issue, link the created/updated issue as a sub-issue (use the issue's **node ID**, not its number) 6. For parent/sub-issue management: - To list sub-issues: get the parent issue's sub-issues - To add a sub-issue: pass the parent issue number and the child's node ID - To remove a sub-issue: unlink the child from the parent - To reorder sub-issues: reprioritise with `after_id` or `before_id` - When creating multiple related issues, prefer structuring them as a parent with sub-issues rather than flat independent issues 7. For queries: - Fetch a specific issue by number - Inspect sub-issue hierarchy on a parent issue - Search issues for filters, keywords, and cross-repo lookups - List repository issues 8. For comments: - Fetch issue context first when needed - Add the comment to the issue 9. Display a summary with issue links and what changed ## Validation - For titles: follow `rules/issue-title.md` - For body with template: follow `rules/template-adherence.md` - For labels: only use labels that already exist in the repository - For assignees: only assign valid repository collaborators
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.