Get the FREE Ultimate OpenClaw Setup Guide →

fix-github-issue

Scanned
npx machina-cli add skill AgnosticUI/agnosticui/fix-github-issue --openclaw
Files (1)
SKILL.md
2.9 KB

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

Source

git clone https://github.com/AgnosticUI/agnosticui/blob/master/.claude/skills/fix-github-issue/SKILL.mdView on GitHub

Overview

This skill automates fixing a GitHub issue by number using a structured, approval-driven workflow. It guides you through creating a feature branch, analyzing the issue, implementing changes, and preparing clear commits and a PR aligned with AgnosticUI conventions.

How This Skill Works

Invoke /fix-github-issue ISSUE_NUMBER to start. It reads PROJECT_CONTEXT to follow AgnosticUI conventions, verifies a clean git state, and creates a feature branch named issue-<ISSUE_NUMBER>/<short-description> (pending your approval). It then uses gh issue view to fetch details and scans the codebase (v2/lib/src/components and related playgrounds) to locate root causes and propose changes. After you approve, it implements the fix, updates tests/docs as needed, and prepares a descriptive commit before pushing and opening a PR.

When to Use It

  • You need to fix a specific GitHub issue by its number and follow a branch-based workflow.
  • You want to view issue details, reproduction steps, and expected behavior before coding.
  • You need to propose changes and require explicit approval before modifying code.
  • You're ready to implement changes after approval and create a descriptive commit.
  • You want to push a feature branch and open a PR with a clear message referencing the issue.

Quick Start

  1. Step 1: Run the command /fix-github-issue ISSUE_NUMBER to start
  2. Step 2: Verify a clean git state, create the branch as issue-ISSUE_NUMBER/short-description, and wait for approval before changing code
  3. Step 3: After approval, implement the fix, run tests if applicable, commit with a descriptive message, push, and open a PR

Best Practices

  • 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 descriptive commit messages referencing the issue (e.g., "Fix #123: ...")

Example Use Cases

  • Fix #276: Ensure button variant renders correctly in v2
  • Fix #421: Accessibility fixes for dropdown in React
  • Fix #512: Improve color contrast in dark theme
  • Fix #789: Sync Vue component prop typing
  • Fix #1010: Add missing tests for issue 276 scenario

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers ↗