New: 97,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 yontrack in yontrack/yontrack

Pick a GitHub issue, create a correctly-named branch (claude/<short-description-pipeline), implement the fix, and summarise the changes.

MITAuto-check passed

Install Fix Issue

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

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

GitHub CLI
$ gh skill install yontrack/yontrack 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/yontrack/yontrack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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
102
Token cost
~1.6k tokens
SKILL.md length
702 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Pick a GitHub issue, create a correctly-named branch (claude/<short-description-pipeline), implement the fix, and summarise the changes.

  • Works in 7 steps: Fetch issue details → Derive branch name → Create the branch → …
  • Work on a GitHub issue
  • SKILL.md covers Step 1 — Fetch issue details, Step 2 — Derive branch name, Step 3 — Create the branch and Step 4 — Mark the issue as in…, plus 3 more sections
  • Calls gh and git

What it does

Fix Issue is an agent skill from yontrack/yontrack. Pick a GitHub issue, create a correctly-named branch (claude/<short-description-pipeline), implement the fix, and summarise the changes. Use when asked to fix or work on a GitHub issue.

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

It works with GitHub. The repository describes itself as: Continuous delivery monitoring. The licence is MIT.

When your agent uses it

  • Work on a GitHub issue

Example prompts

  • “/fix-issue”

Requirements

  • Pre-approved tools (allowed-tools): Bash(gh issue view:*), Bash(gh issue list:*), Bash(gh issue edit:*), Bash(gh run list:*), Bash(gh run view:*), Bash(gh run watch:*), Bash(git checkout:*), Bash(git branch:*)

Workflow steps

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

  1. Fetch issue details
  2. Derive branch name
  3. Create the branch
  4. Mark the issue as in progress
  5. Implement the fix
  6. Land on the base, mark the issue ready and close it
  7. Summarise

What it can do on your machine

Read from SKILL.md and the folder at commit ba18b1c. 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(gh issue edit:*)
    • Bash(gh run list:*)
    • Bash(gh run view:*)
    • Bash(gh run watch:*)
    • 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 1.6k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 702 words of instructions outside code blocks.

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

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 yontrack/yontrack at commit ba18b1c, republished under its MIT licence (© yontrack). 702 words, ~1,592 tokens.

Download SKILL.mdSave it as .claude/skills/fix-issue/SKILL.md (or your agent's skills folder).
name
fix-issue
description
Pick a GitHub issue, create a correctly-named branch (claude/<short-description>-pipeline), implement the fix, and summarise the changes. Use when asked to fix or work on a GitHub issue.
allowed-tools
Bash(gh issue view:*), Bash(gh issue list:*), Bash(gh issue edit:*), Bash(gh run list:*), Bash(gh run view:*), Bash(gh run watch:*), Bash(git checkout:*), Bash(git branch:*)
user-invocable
true

/fix-issue — Fix a GitHub Issue

Arguments passed: $ARGUMENTS

Parse $ARGUMENTS for an issue number. If not provided, ask the user for one, or offer to list open issues with gh issue list.

Step 1 — Fetch issue details

bash
gh issue view {number} --json number,title,body,labels

Read the issue title, description, and any linked context. Understand what needs to be fixed before touching any code.

Step 2 — Derive branch name

From the issue title, create a short kebab-case description (2–5 words). The branch name must follow this pattern exactly:

claude/{short-description}-pipeline

Examples:

  • Issue "Fix null pointer in build validation" → claude/fix-null-build-validation-pipeline
  • Issue "Add keepLast support for DISABLE mode" → claude/add-keeplast-disable-mode-pipeline

Step 3 — Create the branch

The base follows the milestone:

  • Any milestone but 5.5, or none: the base is main.

  • Milestone 5.5 — a fix for the 5.x line, maintained on release/5.5. The body's **Base branch:** line says which of the two it is:

    • main, cherry-pick to release/5.5 — the base is main, and Step 6 cherry-picks the commit onto release/5.5 once it has landed. This is the default for a 5.5 issue: a fix living only on the 5.x branch is a regression in 6.x waiting to happen.
    • release/5.5 — the bug exists only in 5.x, in code that 6.0 removed. The base is release/5.5, and there is nothing to cherry-pick.

    A 5.5 issue with no **Base branch:** line takes the first form. doc/dev-guide/patch-release.md has the rules, among them no Flyway migration on release/5.5.

Branch from the freshly fetched remote ref, never from wherever the worktree happens to stand:

bash
git fetch origin            # outside the sandbox - a sandboxed fetch fails and leaves the ref stale
git checkout -b claude/{short-description}-pipeline origin/<base>

Confirm the branch was created and git merge-base HEAD origin/<base> equals git rev-parse origin/<base> before proceeding.

Step 4 — Mark the issue as in progress

As soon as the branch exists, move the issue to the work-in-progress status. An issue carries exactly one status:* label at a time, so always remove the current one in the same command — never add status:wip on its own.

Most issues start on status:todo, which is the usual label to drop:

bash
gh issue edit {number} --add-label "status:wip" --remove-label "status:todo"

If Step 1 showed a different status:* label (status:ready, status:tomerge, status:waiting-feedback, status:released), remove that one instead:

bash
gh issue edit {number} --add-label "status:wip" --remove-label "status:<previous>"

The --json ...,labels output from Step 1 already tells you which one is set — use it rather than guessing.

Step 5 — Implement the fix

Explore the codebase to understand the affected area. Follow all patterns in CLAUDE.md:

  • Use the existing service/repository layer, don't bypass it
  • Apply security checks where needed
  • Add or update unit tests (*Test.kt) and/or integration tests (*IT.kt) as appropriate
  • Follow naming conventions for the module being changed

Commit on the branch, prefixing every subject with the issue number — one #<number> at the very start, then a space:

#{number} Some message

See Commit messages in CLAUDE.md for what that prefix costs in the semantic change log.

Show full SKILL.md (262 more words)Show less

Step 6 — Land on the base, mark the issue ready and close it

Follow the workflow lifecycle in CLAUDE.md: merge the branch into <base>, push, and delete the local branch. Then wait for the CI build on <base> for the pushed commit:

bash
gh run list --workflow=ci.yml --branch <base> --limit 1 --json databaseId,headSha,status,conclusion,url
gh run watch <run-id>

For main, cherry-pick to release/5.5, once that main run is green, cherry-pick the commit onto release/5.5 and wait for that branch's build as well:

bash
git fetch origin            # outside the sandbox
git checkout -b claude/{short-description}-5.5-pipeline origin/release/5.5
git cherry-pick -x <sha on main>
git push origin HEAD:release/5.5
git checkout - && git branch -D claude/{short-description}-5.5-pipeline
gh run list --workflow=ci.yml --branch release/5.5 --limit 1 --json databaseId,headSha,status,conclusion,url
gh run watch <run-id>

A cherry-pick that does not apply cleanly is not resolved by guessing: stop and report it. The base in the close comment below is then main, cherry-picked to release/5.5.

Only when the run's conclusion is success for the commit you pushed — both runs, for a cherry-pick — move the issue to ready and close it, provided it has a milestone:

bash
gh issue view {number} --json milestone --jq '.milestone.title'
gh issue edit {number} --add-label "status:ready" --remove-label "status:wip"
gh issue close {number} --reason completed --comment "Merged into \`<base>\`, ships with <milestone>."

If the issue has no milestone, apply status:ready but leave it open and say so — Damien sets the milestone and closes it. Never guess a milestone. Issue status labels in CLAUDE.md says why.

If the build fails, leave the issue on status:wip, report the failure, and fix it. If the build is still running and waiting is impractical, leave status:wip and say so — never apply status:ready on an unverified build.

Never close the issue at any other point — closing belongs to marking it ready, and nowhere else.

Step 7 — Summarise

After implementing, provide a concise summary:

  • What was changed and in which files
  • What tests cover the fix
  • The branch name, whether it landed on <base> (and was cherry-picked to release/5.5), and the resulting issue status label

Never open a pull request — leave that to the user.

© yontrack, 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 .claude/skills/fix-issue of yontrack/yontrack.

Open the folder on GitHubat commit ba18b1c

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 skillyontrack/yontrack102—~1.6kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Diagnosing Superpowers Sessionsobra/superpowers296k3 repos~1.7kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow83k5 repos~1.3kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Diagnosing Superpowers Sessions

    obra/superpowers

    Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    296k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    83k GitHub starsUsed in 5 repos~1.3k tokens
    Research & ScienceAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

More from yontrack/yontrack

  • Add JSON Schema

    yontrack/yontrack

    Add a new downloadable JSON schema to the Resources page — Kotlin provider class only, auto-discovered by Spring.

    102 GitHub stars~883 tokensUpdated yesterday
    Auto-check passed

  • Add Property Type

    yontrack/yontrack

    Add a complete Yontrack property type — Kotlin PropertyType class, GraphQL mutation provider, and all required frontend UI components (Icon, Display, Form, FormPrepare).

    102 GitHub stars~990 tokensUpdated yesterday
    Auto-check passed

  • Add Widget

    yontrack/yontrack

    Scaffold a new Yontrack dashboard widget end-to-end — Kotlin AbstractWidget class with config data class, and two frontend components (display + form).

    102 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

  • New Extension

    yontrack/yontrack

    Scaffold a new Yontrack extension end-to-end — module, feature descriptor, service, GraphQL, migration, tests, and UI.

    102 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

  • Release Milestone

    yontrack/yontrack

    Mark every status:ready issue of a GitHub milestone as released — swap status:ready for status:released, comment "Available in <version", and close any that are still open (ready issues are normally…

    102 GitHub stars~911 tokensUpdated yesterday
    Auto-check passed

  • Run Initiative

    yontrack/yontrack

    Work through every ready-for-agent issue of a Yontrack initiative, optionally restricted to one milestone, one at a time, each to full completion — branch, implement, merge to the issues' base…

    102 GitHub stars~5.2k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Fix Issue

What does Fix Issue do?

Pick a GitHub issue, create a correctly-named branch (claude/<short-description-pipeline), implement the fix, and summarise the changes. Fix Issue is an agent skill from yontrack/yontrack. Pick a GitHub issue, create a correctly-named branch (claude/<short-description-pipeline), implement the fix, and summarise the changes.

When should I use Fix Issue?

Fix Issue fits situations like: work on a GitHub issue.

How do I install Fix Issue in Claude Code?

Run `npx skills add yontrack/yontrack --skill fix-issue -a claude-code`. Or copy the skill folder (.claude/skills/fix-issue in yontrack/yontrack) 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 yontrack/yontrack --skill fix-issue -a codex`. Or copy the skill folder (.claude/skills/fix-issue in yontrack/yontrack) 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 yontrack/yontrack --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(gh issue edit:*), Bash(gh run list:*), Bash(gh run view:*), Bash(gh run watch:*), 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 1.6k tokens (SKILL.md is roughly 6.4k 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: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Issue?

yontrack (a GitHub organization) maintains it in yontrack/yontrack, which has 102 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 6, 2026.

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