cmd-gh-issue

Included with Lifetime

$97 forever

Create structured GitHub issues from conversation context using gh CLI

General

What this skill does


# Create GitHub Issue from Conversation

Create a well-structured GitHub issue using `gh` CLI, populated with context from the current conversation.

## Instructions

1. **Determine the repo** -- confirm you're inside a git repo with a GitHub remote:

   ```bash
   gh repo view --json nameWithOwner -q '.nameWithOwner'
   ```

   If this fails, ask the user which repo to file against.

2. **Synthesize the conversation** into a GitHub issue body following the structure below.

3. **Create the issue** using `gh`:

   ```bash
   gh issue create --title "<concise title>" --body "$(cat <<'ISSUE_EOF'
   <issue body here>
   ISSUE_EOF
   )"
   ```

4. **Report back** with the issue URL.

## Issue Body Structure

Build the issue body in this exact order:

### Section 1: What & Why

Open with a short (2-4 bullet) summary answering:

- **What** needs to happen?
- **Why** does it matter? (user pain, system constraint, business goal)

This section should stand alone -- a reader who stops here should understand the ask.

### Section 2: Context & Discussion

This is the bulk of the issue. Capture everything relevant from our conversation:

- **Background** -- what led to this discussion
- **Current behavior** -- how things work today (or don't)
- **Desired behavior** -- what success looks like
- **Constraints & decisions** -- trade-offs we discussed, options we rejected and why
- **Technical details** -- relevant code paths, configs, schemas, API shapes, error messages
- **Related work** -- links to PRs, issues, docs, or external references mentioned

**Formatting rules for this section:**

- Use `## Headings` and `### Subheadings` to organize by topic
- Use bullet points over paragraphs
- Use markdown tables for comparisons, option matrices, or structured data
- Embed images/screenshots if any were shared (use `![alt](url)` syntax)
- Wrap code snippets, commands, file paths, and config in fenced code blocks with language tags
- Use `<details><summary>...</summary>...</details>` to collapse verbose content (logs, full configs, large code blocks) so the issue stays scannable
- Do NOT strip context -- preserve the substance of our discussion, but reorganize it logically

### Section 3: Implementation Plan

End with the plan we've aligned on (even if rough). Frame it for a future agent or developer picking this up cold:

- Number the steps
- Call out key files to create or modify
- Note any open questions or decisions still TBD (prefix with `[ ]`)
- If there are dependencies between steps, make the order explicit
- If we haven't aligned on a plan yet, write `## Implementation Plan\n\n_TBD -- no plan agreed on yet._`

## Labels & Assignment (optional)

- If the conversation implies a category (bug, feature, enhancement, tech-debt), add `--label` flags
- Do NOT assign unless the user explicitly asks

## Style Rules

- **Title**: imperative mood, under 70 chars (e.g., "Add retry logic to webhook delivery")
- **No fluff**: skip filler phrases like "It would be great if..." -- be direct
- **Bias to structure**: headers > paragraphs, bullets > prose, tables > lists-of-pairs
- **Preserve signal**: don't summarize away details that a future implementer would need
- **Mark uncertainty**: if something was discussed but not decided, say so explicitly with "TBD" or an open checkbox `[ ]`

Files: 1

Size: 3.4 KB

Complexity: 10/100

Category: General

Source: https://github.com/olshansk/agent-skills/tree/main/skills/cmd-gh-issue

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts