Official agent skill

Fix Issue

by docker in docker/docs

Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR.

OfficialApache-2.0Auto-check passedDevelopment

Install Fix Issue

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

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

GitHub CLI
$ gh skill install docker/docs 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/docker/docs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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
4.7k
Token cost
~595 tokens
SKILL.md length
284 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
Apache-2.0

At a glance

Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR.

  • Works in 8 steps: Triage → Act on the triage result → Research → …
  • Asked to fix an issue: fix issue 1234
  • SKILL.md covers 1. Triage, 2. Act on the triage result, 3. Research and 4. Write, plus 4 more sections
  • Calls gh and git

What it does

Fix Issue is an agent skill from docker/docs, published by the product's own GitHub organization. Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR. Use when asked to fix an issue: "fix issue 1234", "resolve 500", "create a PR for issue 200".

Its SKILL.md is about 600 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 Development. It works with GitHub. The repository describes itself as: Source repo for Docker's Documentation. The licence is Apache-2.0.

When your agent uses it

  • Asked to fix an issue: fix issue 1234
  • Create a PR for issue 200

Example prompts

  • “fix issue 1234”
  • “resolve 500”
  • “create a PR for issue 200”
  • “/fix-issue”

Requirements

  • Docker

Workflow steps

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

  1. Triage
  2. Act on the triage result
  3. Research
  4. Write
  5. Review
  6. Create PR
  7. Return to main
  8. Report

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    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 595 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 284 words of instructions outside code blocks.

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

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 docker/docs at commit 7ba25ee, republished under its Apache-2.0 licence (© docker). 284 words, ~595 tokens.

Download SKILL.mdSave it as .claude/skills/fix-issue/SKILL.md (or your agent's skills folder).
name
fix-issue
description
Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR. Use when asked to fix an issue: "fix issue 1234", "resolve #500", "create a PR for issue 200".
argument-hint
<issue-number>

Fix Issue

Given GitHub issue $ARGUMENTS, decide what to do with it and either close it or fix it. This skill orchestrates the composable skills — it owns the decision tree, not the individual steps.

1. Triage

Invoke /triage-issue $ARGUMENTS to understand the issue and decide what to do. This runs in a forked subagent and returns a verdict.

2. Act on the triage result

If triage says close it — comment with the reason and close:

bash
gh issue close $ARGUMENTS --repo docker/docs \
  --comment "<one sentence explaining why>

Generated by <active coding agent name>"

Done.

If triage says escalate upstream — comment noting the repo and stop:

bash
gh issue comment $ARGUMENTS --repo docker/docs \
  --body "This needs to be fixed in <upstream-repo>.

Generated by <active coding agent name>"

Done.

If triage says leave it open — comment explaining what was checked and what's unclear. Do not close. Done.

End every issue comment with an accurate agent-disclosure footer that names the active coding agent, for example Generated by Codex or Generated by Claude Code.

If triage says fix it — proceed to step 3.

3. Research

Invoke /research to locate affected files, verify facts, and identify the fix. The issue context carries over from triage. This runs inline — findings stay in conversation context for the write step.

If research reveals the issue is upstream or cannot be fixed (e.g. unverifiable URLs), comment on the issue and stop.

4. Write

Invoke /write to create a branch, make the change, format, self-review, and commit.

5. Review

Invoke /review-changes to check the diff for correctness, coherence, and mechanical compliance. This runs in a forked subagent with fresh context.

If issues are found, fix them and re-review until clean.

6. Create PR

Invoke /create-pr to push the branch and open a pull request.

7. Return to main

bash
git checkout main

8. Report

Summarize what happened: the issue number, what was done (closed, escalated, fixed with a PR link), and why — in a sentence or two.

© docker, Apache-2.0. 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 .agents/skills/fix-issue of docker/docs.

Open the folder on GitHubat commit 7ba25ee

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 skilldocker/docs4.7k—~595Automated safety check: PassApache-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Summarise Ecosystem Resultsastral-sh/ruff50k1 repos~2.2kAutomated safety check: PassMIT

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
  • 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
  • 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
  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Official

    A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…

    50k GitHub starsUsed in 1 repo~2.2k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

More from docker/docs

All 13 skills in this repo
  • Official

    Audit a documentation site for agent-friendliness: discovery, markdown delivery, crawlability, semantic structure, machine-readable surfaces, and content legibility.

    4.7k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Official

    Handle Hugo docs information-architecture moves: discover old vs new URLs, add front matter aliases (Phase 1), update in-repo links (Phase 2), interactive List 2 resolution and fragment validation…

    4.7k GitHub stars~5.1k tokensUpdated today
    Auto-check passed
  • Write

    docker/docs

    Official

    Write or edit reader-facing technical prose for immediate comprehension.

    4.7k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Create Lab Guide

    docker/docs

    Official

    Clone a dockersamples Labspace repo, extract learning objectives and module structure from labspace.yaml, and produce a Hugo guide page under content/guides/ with correct frontmatter…

    4.7k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Curate Whats New

    docker/docs

    Official

    Curate noteworthy Docker launches from documentation pull requests merged during a requested period.

    4.7k GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Maintain PR

    docker/docs

    Official

    Maintain and follow up on a single Docker documentation pull request that you own or are responsible for updating.

    4.7k GitHub stars~825 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Fix Issue

What does Fix Issue do?

Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR. Fix Issue is an agent skill from docker/docs, published by the product's own GitHub organization. Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR.

When should I use Fix Issue?

Fix Issue fits situations like: asked to fix an issue: fix issue 1234; create a PR for issue 200.

How do I install Fix Issue in Claude Code?

Run `npx skills add docker/docs --skill fix-issue -a claude-code`. Or copy the skill folder (.agents/skills/fix-issue in docker/docs) 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 docker/docs --skill fix-issue -a codex`. Or copy the skill folder (.agents/skills/fix-issue in docker/docs) 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 docker/docs --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). Our summary lists: Docker.

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 Apache-2.0 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 595 tokens (SKILL.md is roughly 2.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), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Issue?

docker (a GitHub organization, an official publisher) maintains it in docker/docs, which has 4,667 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

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