New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Fix Issue

by poshan0126 in poshan0126/dotclaude

Take a GitHub issue from number to tested fix — read the issue and comments, reproduce, locate the cause, fix with a regression test, and prep a PR that closes it.

MITAuto-check passedTesting & QA

Install Fix Issue

skills CLI
$ npx skills add poshan0126/dotclaude --skill fix-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install poshan0126/dotclaude fix-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/poshan0126/dotclaude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/fix-issue .claude/skills/fix-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fix-issue
GitHub stars
871
Token cost
~819 tokens
SKILL.md length
446 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Take a GitHub issue from number to tested fix — read the issue and comments, reproduce, locate the cause, fix with a regression test, and prep a PR that closes it.

  • Works in 5 steps: Understand the issue → Classify and branch → Locate and fix → …
  • Testing & QA work in your project
  • SKILL.md covers Step 1: Understand the issue, Step 2: Classify and branch, Step 3: Locate and fix and Step 4: Verify against the issue, plus 2 more sections
  • Calls gh and git

What it does

Fix Issue is an agent skill from poshan0126/dotclaude. Take a GitHub issue from number to tested fix — read the issue and comments, reproduce, locate the cause, fix with a regression test, and prep a PR that closes it.

Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA. It works with GitHub. The repository describes itself as: The standard .claude/ folder structure for everyday development. The licence is MIT.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/fix-issue”

Requirements

  • Pre-approved tools (allowed-tools): Bash(gh issue view *), Bash(gh issue list *), Bash(git status), Bash(git diff *), Bash(git log *), Bash(git checkout *), Bash(git branch *)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Understand the issue
  2. Classify and branch
  3. Locate and fix
  4. Verify against the issue
  5. Ship it

What it can do on your machine

Read from SKILL.md and the folder at commit 94b84b9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(gh issue view *)
    • Bash(gh issue list *)
    • Bash(git status)
    • Bash(git diff *)
    • Bash(git log *)
    • Bash(git checkout *)
    • Bash(git branch *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fix Issue loads about 819 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 446 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~819

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from poshan0126/dotclaude at commit 94b84b9, republished under its MIT licence (© poshan0126). 446 words, ~819 tokens.

Download SKILL.mdSave it as .claude/skills/fix-issue/SKILL.md (or your agent's skills folder).
name
fix-issue
description
Take a GitHub issue from number to tested fix — read the issue and comments, reproduce, locate the cause, fix with a regression test, and prep a PR that closes it.
allowed-tools
Bash(gh issue view *), Bash(gh issue list *), Bash(git status), Bash(git diff *), Bash(git log *), Bash(git checkout *), Bash(git branch *)
argument-hint
[issue number or URL]
disable-model-invocation
true

Work a GitHub issue end to end. $ARGUMENTS is the issue number or URL; if omitted, run gh issue list --assignee @me --state open and ask which one.

Step 1: Understand the issue

The live issue thread (or your open assigned issues, when no number was given) is injected below — no need to fetch it again:

!gh issue view $ARGUMENTS --comments 2>/dev/null || gh issue list --assignee @me --state open 2>/dev/null || echo "(no issue arg — paste the issue details)"

  • The thread above is the real spec — read the body AND the discussion; the decision that changes the fix is often in comment 7.
  • Extract: expected behavior, actual behavior, reproduction steps, acceptance criteria, and any decisions already made in the thread.
  • If the issue is ambiguous on something that changes the fix (which behavior is correct? which platform?), ask the user — do NOT guess and do NOT ask in the issue thread without being told to.

Step 2: Classify and branch

  • Bug → follow /debug-fix discipline: reproduce it first (failing test or manual repro), then investigate. No fix before reproduction.
  • Small feature / chore → follow /tdd discipline if a test runner exists: failing test, minimum code, refactor.
  • Propose a branch named fix/issue-$NUMBER-<slug> (or feat/...), matching any existing convention visible in git branch -a. Confirm before creating.

Step 3: Locate and fix

  • Find the code path from the symptoms: grep for the error message, the feature's entry point, or names from the issue.
  • Make the smallest change that satisfies the acceptance criteria. Resist adjacent refactoring — note it for a follow-up instead.
  • Every bug fix ships with a regression test that fails on the old code. If you can't write one, say why in the PR body.
Show full SKILL.md (165 more words)Show less

Step 4: Verify against the issue

  • Re-run the reproduction from Step 1 — confirm the reported behavior is gone.
  • Run the tests for the touched area, then lint/typecheck.
  • Walk the acceptance criteria one by one; quote each with its status.

Step 5: Ship it

  • Hand off to /ship (or follow its discipline): commit message and PR body must include Fixes #$NUMBER so the merge auto-closes the issue.
  • PR body: one-line cause, one-line fix, the regression test, and anything from the issue thread that influenced the approach.
  • After the PR exists, offer to comment the PR link on the issue (gh issue comment — requires confirmation; it's outward-facing).

Rules

  • Never start coding before Step 1 is complete — the thread often contains a decision that invalidates the obvious fix.
  • One issue per branch per PR. If the issue is really three issues, say so and fix the one that was asked.
  • If reproduction is impossible (can't access the environment, missing credentials), report exactly what's missing instead of fixing blind.

© poshan0126, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/fix-issue of poshan0126/dotclaude.

Open the folder on GitHubat commit 94b84b9

Compare with similar skills

Fix Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fix Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix Issue this skillposhan0126/dotclaude871—~819Automated safety check: PassMIT
Triage IssuesClickHouse/clickhouse-java1.6k—~904Automated safety check: PassApache-2.0
Issue To Regression Testbrunosabot/streamline-card269—~529Automated safety check: PassMIT
Gh IssuesTypedDevs/bashunit4341 repos~1.7kAutomated safety check: NotesMIT
Nemoclaw Maintainer Analyze CI PerformanceNVIDIA/NemoClaw23k—~644Automated safety check: PassApache-2.0
Reprovaadin/web-components582—~1.3kAutomated safety check: PassNone

Similar skills

  • Triage Issues

    ClickHouse/clickhouse-java

    Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.

    1.6k GitHub stars~904 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Issue To Regression Test

    brunosabot/streamline-card

    A skill your agent uses when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix.

    269 GitHub stars~529 tokensUpdated 4 mo ago
    Testing & QAAuto-check passed

  • Gh Issues

    TypedDevs/bashunit

    Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the /gh-issue skill, sequentially.

    434 GitHub starsUsed in 1 repo~1.7k tokens
    Testing & QAAuto-check: notes

  • Nemoclaw Maintainer Analyze CI Performance

    NVIDIA/NemoClaw

    Official

    Analyze retained NemoClaw CI timings for slow CLI tests, runner queues, or base-image publication.

    23k GitHub stars~644 tokensUpdated today
    Testing & QAAuto-check passed

  • Repro

    vaadin/web-components

    Reproduce a Vaadin web component bug from a GitHub issue in vaadin/web-components.

    582 GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Fix Random CI Test Failure

    dotnet/macios

    Official

    Investigate and fix flaky/random CI test failures in dotnet/macios.

    2.9k GitHub stars~1.3k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from poshan0126/dotclaude

All 14 skills in this repo

  • Session Catchup and Handoff

    poshan0126/dotclaude

    Rebuilds working context after /clear by reading a handoff note and the branch's git state, or writes that handoff note before a session ends.

    871 GitHub stars~811 tokensUpdated 1 mo ago
    Auto-check passed

  • Context Budget Check

    poshan0126/dotclaude

    Estimates the per-turn token cost of a project's .claude folder and CLAUDE.md, split into always-loaded, path-scoped and invoked-only files, and flags what runs over budget.

    871 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Codebase Onboarding Tour

    poshan0126/dotclaude

    Builds a quick mental model of an unfamiliar codebase by dispatching read-only Explore subagents and merging their findings into one brief.

    871 GitHub stars~858 tokensUpdated 1 mo ago
    Auto-check passed

  • Parallel Specialist PR Review

    poshan0126/dotclaude

    Reviews a pull request, staged changes or a file by sending the diff to specialist reviewer agents in parallel, then merges their findings into one compact report.

    871 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

  • dotclaude Project Setup

    poshan0126/dotclaude

    Scans a codebase, interviews you, and installs only the justified Claude Code rules, hooks, agents and skills, tailored to the project's stack.

    871 GitHub stars~3.6k tokensUpdated 1 mo ago
    Auto-check passed

  • Ship Changes

    poshan0126/dotclaude

    Walks through commit, push and pull request creation for the current changes, asking you to confirm the files, message, push and PR text at each step.

    871 GitHub stars~953 tokensUpdated 1 mo ago
    Auto-check: notes

Works with

Categories

Questions about Fix Issue

What does Fix Issue do?

Take a GitHub issue from number to tested fix — read the issue and comments, reproduce, locate the cause, fix with a regression test, and prep a PR that closes it. Fix Issue is an agent skill from poshan0126/dotclaude. Take a GitHub issue from number to tested fix — read the issue and comments, reproduce, locate the cause, fix with a regression test, and prep a PR that closes it.

When should I use Fix Issue?

Fix Issue fits situations like: testing & QA work in your project.

How do I install Fix Issue in Claude Code?

Run `npx skills add poshan0126/dotclaude --skill fix-issue -a claude-code`. Or copy the skill folder (skills/fix-issue in poshan0126/dotclaude) into .claude/skills/fix-issue in your project. Claude Code loads it when a task matches its description.

How do I install Fix Issue in Codex?

Run `npx skills add poshan0126/dotclaude --skill fix-issue -a codex`. Or copy the skill folder (skills/fix-issue in poshan0126/dotclaude) into .agents/skills/fix-issue in your project. Codex loads it when a task matches its description.

Can I use Fix Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add poshan0126/dotclaude --skill fix-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-issue, .gemini/skills/fix-issue, .github/skills/fix-issue and .opencode/skills/fix-issue in your project.

What does Fix Issue need to run?

Going by SKILL.md and its folder, Fix Issue needs the command-line tools its instructions call (gh and git). Its frontmatter pre-approves these tools: Bash(gh issue view *), Bash(gh issue list *), Bash(git status), Bash(git diff *), Bash(git log *), Bash(git checkout *), Bash(git branch *).

Does Fix Issue access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Fix Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fix Issue use?

Fix Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fix Issue use?

About 819 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fix Issue?

Skills that share tags, products or a category with Fix Issue: Triage Issues (ClickHouse/clickhouse-java, 1.6k stars), Issue To Regression Test (brunosabot/streamline-card, 269 stars), Gh Issues (TypedDevs/bashunit, 434 stars) and Nemoclaw Maintainer Analyze CI Performance (NVIDIA/NemoClaw, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Issue?

poshan0126 (a GitHub user) maintains it in poshan0126/dotclaude, which has 871 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on August 27, 2026.

Source: poshan0126/dotclaude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.