AugmentClaude
FrontendTesting

GitHub Issue Fixer

By AgnosticUI· AgnosticUI/agnosticui· 0

Fix GitHub issues by number following project best practices.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.
    Install
    Sign up to copy
    Sign up free to reveal

    This copies the whole skill folder into ~/.claude/skills/fix-github-issue-agnosticui/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
    Sign up free to reveal
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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

What this skill does

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:

  1. 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

  2. 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

  3. Analyze the issue:

    • Use gh issue view $ARGUMENTS to fetch full issue details
    • Understand the problem, reproduction steps, and expected behavior

  4. 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

  5. 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

  6. 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

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

  8. 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

Related skills

G

Generative Code Art

anthropics

Create algorithmic art with p5.js using randomness and interactive parameters.

OfficialComplete terms in LICENSE.txt
U

UI/UX Pro Max

anthropics

Build production-grade web components and interfaces with distinctive, polished design.

OfficialComplete terms in LICENSE.txt
A

Artifact Theme Toolkit

anthropics

Apply professional color and font themes to slides, docs, and web pages.

OfficialComplete terms in LICENSE.txt
M

Multi-Component Web Artifacts

anthropics

Build complex React artifacts with Tailwind CSS and shadcn/ui components.

OfficialComplete terms in LICENSE.txt