gh-start

Start Work on Issue #$ARGUMENTS

Complete workflow from issue assignment through implementation. Ends with option to create PR via /gh-pr or continue working.

Tool Usage: This workflow uses the AskUserQuestion tool for interactive dialogues at key decision points.

Phase 1: Setup

1. Fetch the issue:

   gh issue view $ARGUMENTS
   

2. Fetch all issue comments for full context:

   REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
   gh api repos/$REPO/issues/$ARGUMENTS/comments --jq '.[] | "---\n**@\(.user.login)** on \(.created_at):\n\(.body)\n"'
   

3. Assign the issue to yourself:

   gh issue edit $ARGUMENTS --add-assignee @me
   

4. Ensure on latest main:

   git checkout main && git pull origin main
   

5. Determine branch type - If ambiguous, use the AskUserQuestion tool:

   When issue type is unclear (could be feature or fix), ask:

   • Option 1: "feature/issue-{number}-{desc}" - New functionality
   • Option 2: "fix/issue-{number}-{desc}" - Bug fix
   • Option 3: "docs/issue-{number}-{desc}" - Documentation only

   git checkout -b {branch-name}
   

6. Confirm setup with user before beginning implementation

Phase 2: Implementation

• Work through the issue requirements systematically
• Follow CLAUDE.md guidelines for content patterns
• For plugin changes, ensure plugin.json and marketplace.json stay in sync
• Review Markdown formatting for consistency

Phase 3: Quality Checks

1. Verify all acceptance criteria in the issue are met

2. Run plugin validation (if plugin files changed):

   ls plugins/*/  # Check plugin directories exist
   cat plugins/*/.claude-plugin/plugin.json  # Verify plugin.json valid
   

3. Commit with conventional format:

   • feat: for features
   • fix: for bug fixes
   • docs: for documentation
   • refactor: for refactoring
   • chore: for maintenance