create-issue

Create a GitHub issue for the current repository based on the user's input.

Instructions

1. Determine Issue Type - Based on the user's description, pick one:

   • Bug: Defects or unexpected behavior
   • Task: Specific, bounded work items that can be completed in one PR
   • Feature: Request a new capability (no design required)
   • RFC: Propose a design for discussion before implementation
   • Spec: Approved implementation plan ready for execution

   Confirm what this repo actually offers before assuming — ls .github/ISSUE_TEMPLATE/ for the templates and gh issue create --help for whether --type is supported.

2. Gather Context - If the user provides a file path or references existing code:

   • Read the relevant files to understand the current implementation
   • Check related configuration files
   • Review any referenced documentation

3. Draft the Issue - Read the matching YAML template in .github/ISSUE_TEMPLATE/ and mirror its structure. Each template declares its own type: in frontmatter and marks which fields are required — read the file rather than guessing the sections. Fill the optional fields too where you have the information; they're the ones that make an issue actionable later.

   Note gh issue create --title/--body bypasses templates entirely — nothing prefills and nothing validates. That's exactly why the body has to be hand-matched to the template structure.

4. Sanitize for Public Visibility - This repo is public and the issue is world-readable immediately. Before creating:

   • Remove any internal pricing, margins, or cost details
   • Remove specific customer names or data
   • Generalize any sensitive business metrics
   • For anything security-adjacent, keep the text terse and non-actionable — no exploit mechanics, no affected-endpoint enumerations, no payloads. Detailed root-cause belongs in the private vault, referenced by filename only; for coordinated disclosure use a private GitHub Security Advisory, never a public issue.
   • Keep ordinary technical implementation details (these are fine to share)

5. Create the Issue - One command, with the type set inline:

   gh issue create \
     --type <Bug|Task|Feature|RFC|Spec> \
     --title "<clear, concise title>" \
     --body-file /tmp/issue-body.md \
     --label "<labels>"
   

   No prefixes like [SPEC] in the title — the type handles categorization. Write the body to a file rather than inlining it, to avoid shell-escaping problems.

   To change the type on an existing issue: gh issue edit <n> --type <Type> (or --remove-type). The old GraphQL updateIssue mutation is no longer needed for either case.