fix-github-issue

**Usage:** `/fix-github-issue ISSUE_NUMBER` **Example:** `/fix-github-issue 276` Fix GitHub issue $ARGUMENTS following best practices. **Setup:** 1. Read `.claude/PROJECT_CONTEXT.md` for AgnosticUI structure, conventions, and workflows **Steps:** 2. **Verify we're starting from a clean state:** - Check `git status` to ensure working directory is clean - Confirm we're on `master` branch - If not clean or on wrong branch, STOP and ask user to resolve 3. **Create a feature branch:** - Follow convention from PROJECT_CONTEXT: `issue-$ARGUMENTS/descriptive-name` - Example: `issue-276/fix-button-variant` - Use `git checkout -b issue-$ARGUMENTS/[short-description]` - **WAIT FOR USER APPROVAL of branch name** 4. **Analyze the issue:** - Use `gh issue view $ARGUMENTS` to fetch full issue details - Understand the problem, reproduction steps, and expected behavior 5. **Investigate the codebase:** - Use PROJECT_CONTEXT to identify relevant locations: - Core components in `v2/lib/src/components/` - Framework implementations in playgrounds - Related tests and examples - Use Read, Grep, and Glob to find relevant files - Review current implementation and identify root cause 6. **Propose the fix:** - Explain what needs to change and why - Consider impact across Lit, React, and Vue if applicable - Follow AgnosticUI's CSS-first, accessibility-focused principles - Show the user your proposed changes - **WAIT FOR USER APPR...