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 analogjs in analogjs/analog

End-to-end flow for resolving a GitHub issue — fetch and understand the issue, create a feature branch off beta, implement and verify the fix, then hand off to the open-pr skill.

MITAuto-check passedDevelopment

Install Fix Issue

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

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

GitHub CLI
$ gh skill install analogjs/analog 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/analogjs/analog.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
3.2k
Token cost
~808 tokens
SKILL.md length
435 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

End-to-end flow for resolving a GitHub issue — fetch and understand the issue, create a feature branch off beta, implement and verify the fix, then hand off to the open-pr skill.

  • Works in 4 steps: Understand the issue → Create a feature branch off beta → Implement the fix → …
  • The user says fix issue <n
  • SKILL.md covers 1. Understand the issue, 2. Create a feature branch off…, 3. Implement the fix and 4. Hand off to open-pr, plus 1 more section
  • Calls git and gh

What it does

Fix Issue is an agent skill from analogjs/analog. End-to-end flow for resolving a GitHub issue — fetch and understand the issue, create a feature branch off beta, implement and verify the fix, then hand off to the open-pr skill. Use when the user says "fix issue <n", "work on issue <n", or wants to take an issue from investigation through to a PR.

Its SKILL.md is about 810 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 and Git. The repository describes itself as: The fullstack meta-framework for Angular. Powered by Vite and Nitro. The licence is MIT.

When your agent uses it

  • The user says fix issue <n
  • Work on issue <n
  • Wants to take an issue from investigation through to a PR

Example prompts

  • “fix issue <n”
  • “work on issue <n”
  • “/fix-issue”

Workflow steps

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

  1. Understand the issue
  2. Create a feature branch off beta
  3. Implement the fix
  4. Hand off to open-pr

What it can do on your machine

Read from SKILL.md and the folder at commit eedd920. 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:

    • git
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, 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 808 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 435 words of instructions outside code blocks.

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

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 analogjs/analog at commit eedd920, republished under its MIT licence (© analogjs). 435 words, ~808 tokens.

Download SKILL.mdSave it as .claude/skills/fix-issue/SKILL.md (or your agent's skills folder).
name
fix-issue
description
End-to-end flow for resolving a GitHub issue — fetch and understand the issue, create a feature branch off `beta`, implement and verify the fix, then hand off to the open-pr skill. Use when the user says "fix issue <n>", "work on issue <n>", or wants to take an issue from investigation through to a PR.

Drive a GitHub issue from investigation to a ready-to-review fix on a feature branch. This skill owns understanding, branching, and implementing. It hands the commit/push/PR step off to the open-pr skill.

Take the issue number/URL from the user. If none is given, ask for it.

1. Understand the issue

  • gh issue view <n> --json title,body,state,labels,comments,author,createdAt to read it. (Plain gh issue view <n> may fail on Projects-classic GraphQL — prefer the --json form.)
  • Read any linked reproduction repo, error output, and referenced files. Identify the affected package/area.
  • Trace the root cause in the codebase before writing anything — read the relevant source, not just the symptom. Delegate broad searches to the Explore agent when the cause could live in several places.
  • Restate the root cause and intended fix to the user, and confirm the approach before large or behavior-changing edits. Surface trade-offs and regression risks.

2. Create a feature branch off beta

  • Branch from the base branch (beta by default; honor a different base if the user names one). First sync the base with its remote so the new branch starts from the latest tip: git checkout <base> && git pull --ff-only && git checkout -b <type>/<n>-<short-slug> <base> — pick <type> from the change (fix, feat, chore, docs, refactor, test) and a short kebab slug referencing the issue, e.g. fix/2348-dts-in-source.
  • If git pull --ff-only fails (local diverged from remote), stop and surface it to the user — don't force or rebase silently.
  • If the user already created/named a branch, use that instead. Never implement on the base branch.
Show full SKILL.md (183 more words)Show less

3. Implement the fix

  • Make the minimal, well-scoped change that addresses the root cause. Match the surrounding code's style and idioms.
  • Add or update tests when the repo's conventions call for them — but respect explicit user direction (e.g. "no snapshot test").
  • Verify as far as the environment allows: run the affected package's tests/typecheck if dependencies are installed; if they aren't, say so plainly rather than claiming success. Consider the verify or code-review skills for behavior changes.
  • Reason explicitly about regressions: who else hits this code path, and does the change alter their behavior?

4. Hand off to open-pr

  • Once the fix is on the feature branch and verified, invoke the open-pr skill to format, commit (with Closes #<n>), push, and open the PR against beta.
  • Don't duplicate open-pr's logic here — it owns commit message conventions, the PR template, scope mapping, and the outward-facing confirmation.

Notes

  • Keep investigation findings concise but show the evidence (file:line) for the root cause.
  • If the issue turns out to be invalid, already fixed, or a usage question rather than a bug, report that instead of forcing a fix.

© analogjs, 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 .agents/skills/fix-issue of analogjs/analog.

Open the folder on GitHubat commit eedd920

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 skillanalogjs/analog3.2k—~808Automated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0

Similar skills

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    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

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated today
    DevelopmentAuto-check passed

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Mole Release Notes Publisher

    tw93/Mole

    Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    69k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from analogjs/analog

  • Analogjs

    analogjs/analog

    Conventions for working in an AnalogJS app (an Angular meta-framework powered by Vite) — file-based routing with .page.ts files, RouteMeta, server and API routes on Nitro/h3, page load functions and…

    3.2k GitHub stars~891 tokensUpdated today
    Auto-check passed

  • Open PR

    analogjs/analog

    Commit the current work, push the current feature branch, and open a GitHub PR filled out from the repo's PR template.

    3.2k GitHub stars~944 tokensUpdated today
    Auto-check passed

  • Handhold PR

    analogjs/analog

    Watch a PR's CI, diagnose every failing check, fix what's actually broken, resolve CodeRabbit's major findings, and keep iterating until the PR is green.

    3.2k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Investigate Issue

    analogjs/analog

    Investigate a GitHub issue end to end — reproduce the reporter's repo or code snippet in an isolated sandbox outside the monorepo, trace the root cause in the source, and draft a reply back to the…

    3.2k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Fix Issue

What does Fix Issue do?

End-to-end flow for resolving a GitHub issue — fetch and understand the issue, create a feature branch off beta, implement and verify the fix, then hand off to the open-pr skill. Fix Issue is an agent skill from analogjs/analog. End-to-end flow for resolving a GitHub issue — fetch and understand the issue, create a feature branch off beta, implement and verify the fix, then hand off to the open-pr skill.

When should I use Fix Issue?

Fix Issue fits situations like: the user says fix issue <n; work on issue <n; wants to take an issue from investigation through to a PR.

How do I install Fix Issue in Claude Code?

Run `npx skills add analogjs/analog --skill fix-issue -a claude-code`. Or copy the skill folder (.agents/skills/fix-issue in analogjs/analog) 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 analogjs/analog --skill fix-issue -a codex`. Or copy the skill folder (.agents/skills/fix-issue in analogjs/analog) 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 analogjs/analog --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 (git and gh).

Does Fix Issue access the network?

SKILL.md contains no URLs. Its commands use git and gh, 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 808 tokens (SKILL.md is roughly 3.2k 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: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Issue?

analogjs (a GitHub organization) maintains it in analogjs/analog, which has 3,187 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.

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