fix-github-issue
/fix-github-issue
Fix a GitHub issue by number. Use when asked to fix GitHub issues.
- Author
- agnosticui ↗
- Repository
- agnosticui ↗
- Licence
- Apache-2.0
- Last repository change
- 30.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.06.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Fix a GitHub issue by number. Use when asked to fix GitHub issues.
Original author description
Fix a GitHub issue by number. Use when asked to fix GitHub issues.
How it works
SKILL.md has no level-two headings · 67 lines, 372 words
SKILL.md preview
---
name: fix-github-issue
description: Fix a GitHub issue by number. Use when asked to fix GitHub issues.
disable-model-invocation: true
allowed-tools: Read, Grep, Glob, Bash(gh issue view *), Bash(gh pr view *), Bash(git status), Bash(git diff *), Bash(git log *), Bash(git branch *), Bash(git checkout *)
---
**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 APPROVAL before making any changes**
7. **Implement only after approval:**
- Make the necessary code changes
- Update related files (tests, docs, examples) if needed
- Run tests if applicable (check PROJECT_CONTEXT for test commands)
- Verify the fix addresses the issue
8. **Prepare commit:**
- Stage changes with `git add`
- Create descriptive commit message: "Fix #$ARGUMENTS: [description]"
- Show the user what will be committed
- **WAIT FOR USER APPROVAL before committing**
9. **Inform user about next steps:**
- Remind user they're on branch `issue-$ARGUMENTS/...`
- Explain they should review changes with `git diff master`
- When ready, they can: `git push -u origin issue-$ARGUMENTS/...`
- Then create PR with: `gh pr create --base master --head issue-$ARGUMENTS/...`
**Important Rules:**
- **ALWAYS create a feature branch - NEVER work directly on master**
- **NEVER push to remote without explicit user permission**
- **ALWAYS show proposed changes before implementing**
- **STOP and ask for approval at each major step**
- Use clear, descriptive commit messages that reference the issue
- Follow AgnosticUI conventions from PROJECT_CONTEXT
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · agnosticui/agnosticui | 88 | Apache-2.0 |
| simiancraft/simiancraft-skills | 100 | MIT |
| drvoss/everything-copilot-cli | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 53bf328a0ca8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100fix-issue
Fetches a GitHub issue by number, analyzes the requirements, finds the relevant code, implements a fix, and optionally creates a PR. Use when working through your issue backlog. - 100fix-issue
Fix bugs reported in PyTorch GitHub issues by reproducing, root-causing, and implementing a fix in the local working tree. Use when the user asks to fix a PyTorch GitHub issue. - 90fix-issue
Use when fixing a GitHub issue — reproduce, trace root cause, fix, add regression test - 100fix-issue
Analyze and fix a GitHub issue for the iam-policy-validator project. Use when the user wants to fix a GitHub issue, resolve a bug report, or implement a feature request from an issue. Triggers on "/fix-issue", "fix issue #42", "resolve this GitHub issue", or "work on issue". - 100fix-issue
Fix a GitHub issue in NeMo Speech (NVIDIA-NeMo/Speech). Read the issue, reproduce the bug with a failing test, implement the fix, and verify tests pass. Only opens a PR if the user explicitly asks for it. - 100github-fix-issue
Fix GitHub issues end-to-end — analysis, branch creation, implementation, testing, and PR submission. Use whenever the user mentions fixing a GitHub issue, says "fix issue #123", "work on this issue", "修复 issue", or references a GitHub issue number or URL.