gh-issue

Create GitHub Issue

Create a new GitHub issue following solution-agnostic principles.

Tool Usage: This workflow uses the AskUserQuestion tool extensively for interactive dialogues. Use it to clarify ambiguity, offer choices with tradeoffs, and gather missing context.

Phase 1: Gather Requirements

1. Use the AskUserQuestion tool to gather missing information:

   • Context: What's the background? Why is this needed?
   • Current State: What's the problem? (describe behavior, not implementation)
   • Objective: What should be achieved? (outcomes, not methods)
   • Acceptance Criteria: How do we know it's complete? (observable behavior)

2. Extract keywords from the user's description for duplicate detection

3. Check for milestones:

   gh api repos/{owner}/{repo}/milestones --jq '.[] | "\(.number): \(.title)"'
   

   If milestones exist, use AskUserQuestion tool:

   • Option 1: "No milestone"
   • Option 2: "[Milestone name]" (for each active milestone)

Phase 2: Search for Existing Issues

Before creating a new issue, check for potential duplicates:

1. Search open issues using relevant keywords:

   gh issue list --state open --search "RELEVANT_KEYWORDS"
   

2. Search closed issues (may have already been solved):

   gh issue list --state closed --search "RELEVANT_KEYWORDS"
   

3. If matches found, use the AskUserQuestion tool:

   Present the findings and offer choices:

   • Option 1: Proceed - "Create new issue (these are different enough)"
   • Option 2: View existing - "View issue #{number} instead"
   • Option 3: Cancel - "This is a duplicate, don't create"

   Include in the question: issue numbers, titles, and states of potential duplicates.

4. If related issues found but not duplicates, use AskUserQuestion tool:

   • Option 1: "Create new issue, link as 'Related to #X'"
   • Option 2: "Create new issue without linking"
   • Option 3: "View related issue first"