# Fix Github Issue

> Fix a GitHub issue by number. Use when asked to fix GitHub issues.

- **Type:** Skill
- **Install:** `agentstack add skill-agnosticui-agnosticui-fix-github-issue`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [AgnosticUI](https://agentstack.voostack.com/s/agnosticui)
- **Installs:** 0
- **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [AgnosticUI](https://github.com/AgnosticUI)
- **Source:** https://github.com/AgnosticUI/agnosticui/tree/master/.claude/skills/fix-github-issue
- **Website:** https://agnosticui.com

## Install

```sh
agentstack add skill-agnosticui-agnosticui-fix-github-issue
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

**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

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [AgnosticUI](https://github.com/AgnosticUI)
- **Source:** [AgnosticUI/agnosticui](https://github.com/AgnosticUI/agnosticui)
- **License:** Apache-2.0
- **Homepage:** https://agnosticui.com

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-agnosticui-agnosticui-fix-github-issue
- Seller: https://agentstack.voostack.com/s/agnosticui
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.