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 haumacher in haumacher/phoneblock

Start work on a GitHub issue — verify a clean workspace, read the issue, branch off the correct base (the branch where the fix will ship) as issue-<nr-<short-description, then plan the implementation.

GPL-3.0Auto-check: notesDevelopment

Install Fix Issue

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

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

GitHub CLI
$ gh skill install haumacher/phoneblock 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/haumacher/phoneblock.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
367
Token cost
~1.1k tokens
SKILL.md length
574 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
GPL-3.0

At a glance

Start work on a GitHub issue — verify a clean workspace, read the issue, branch off the correct base (the branch where the fix will ship) as issue-<nr-<short-description, then plan the implementation.

  • Works in 5 steps: Ensure the workspace is clean → Read the issue → Fetch the current state → …
  • The user says fix issue 123
  • SKILL.md covers Step 1 — Ensure the workspace…, Step 2 — Read the issue, Step 3 — Fetch the current state and Step 4 — Create and switch to…, plus 1 more section
  • Calls git and gh

What it does

Fix Issue is an agent skill from haumacher/phoneblock. Start work on a GitHub issue — verify a clean workspace, read the issue, branch off the correct base (the branch where the fix will ship) as issue-<nr-<short-description, then plan the implementation. Use when the user says "fix issue 123", "work on issue

Its SKILL.md is about 1.1k 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: Der Spam-Filter für Dein Telefon. The licence is GPL-3.0.

When your agent uses it

  • The user says fix issue 123

Example prompts

  • “fix issue 123”
  • “/fix-issue”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Glob, Grep, WebFetch

Workflow steps

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

  1. Ensure the workspace is clean
  2. Read the issue
  3. Fetch the current state
  4. Create and switch to the issue branch
  5. Decide: implement directly or plan

What it can do on your machine

Read from SKILL.md and the folder at commit 9287ad7. 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
    • Read
    • Glob
    • Grep
    • WebFetch

    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 1.1k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 574 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Glob, Grep, WebFetch

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 haumacher/phoneblock at commit 9287ad7, republished under its GPL-3.0 licence (© haumacher). 574 words, ~1,073 tokens.

Download SKILL.mdSave it as .claude/skills/fix-issue/SKILL.md (or your agent's skills folder).
name
fix-issue
description
Start work on a GitHub issue — verify a clean workspace, read the issue, branch off the correct base (the branch where the fix will ship) as issue-<nr>-<short-description>, then plan the implementation. Use when the user says "fix issue 123", "work on issue
allowed-tools
Bash, Read, Glob, Grep, WebFetch

Start Work on a GitHub Issue

Prepares a clean, correctly-branched workspace for a GitHub issue, then either implements a trivial fix directly or produces a plan when the solution is open.

The issue is given as an argument: a bare number (123), a #-prefixed number (#123), or a full GitHub URL. Extract the number. If no argument was given, ask the user which issue to work on before doing anything else.

This repository has several remotes; origin is haumacher/phoneblock. Always target origin explicitly — never assume a single remote.

Step 1 — Ensure the workspace is clean

Run git status --porcelain.

  • Clean (no output): continue to step 2.
  • Not clean: do not proceed. Run git status and git diff --stat (plus git stash list if relevant), describe the uncommitted/untracked changes to the user, and ask what to do with them (e.g. commit, stash, discard, or proceed on a branch from the current commit). Wait for the answer before continuing — never stash, commit, or discard on your own initiative.

Step 2 — Read the issue

bash
gh issue view <nr> --repo haumacher/phoneblock --comments

Read the title, body, and comments so you understand what is actually being asked. If the issue is closed or cannot be found, stop and tell the user.

Step 3 — Fetch the current state

bash
git fetch origin --tags

This makes every up-to-date base candidate (all origin/* branches and tags) available locally before the branch is created.

Step 4 — Create and switch to the issue branch

Create the branch before investigating any code. Analysing the repository at whatever commit happens to be checked out is meaningless — you must first be on the base where the fix will actually ship, then study that code. So decide the base branch now, from the issue alone; do not open source files to make this choice.

Pick the base branch = where the fix will ship. Usually this is origin/master. But some work ships on a maintenance or release line and must branch from there instead — for example dongle firmware fixes destined for a release branch off dongle-X.Y.x (or its rc tag), per CLAUDE.md's Dongle Release Branches policy. Determine the target from the issue: which component it touches and which release it is meant for. If the correct base is not obvious (e.g. it could be master or a release line), ask the user before branching — do not default to origin/master silently.

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

Derive a short, kebab-case description (~3–5 words, lowercase, ASCII) from the issue title. Branch name schema:

issue-<nr>-<short-description>

Example: issue 142 "CardDAV sync fails for long contact names" → issue-142-carddav-long-contact-names.

Create the branch from the chosen base and switch to it (substitute the base you picked for <base>, e.g. origin/master or dongle-1.4.x):

bash
git checkout -b issue-<nr>-<short-description> <base>

If a branch with that name already exists, mention it and ask the user whether to reuse it, pick a different suffix, or replace it.

Step 5 — Decide: implement directly or plan

Investigate the codebase as needed (CLAUDE.md describes the module layout) and judge how clear-cut the fix is:

  • Trivial / unambiguous — small change with one obvious correct solution (typo, clear bug with a single fix, a well-specified minor feature). Implement it directly, then verify (build/tests as appropriate) and report the result. No need to ask first.
  • Open or non-trivial — the change is large, touches many areas, or there are several plausible solution alternatives with real trade-offs. Produce a concrete implementation plan (which files change, the approach chosen, alternatives considered, open questions), present it with ExitPlanMode, and wait for approval before editing files.

When in doubt between the two, prefer planning and asking.

© haumacher, GPL-3.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 .claude/skills/fix-issue of haumacher/phoneblock.

Open the folder on GitHubat commit 9287ad7

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 skillhaumacher/phoneblock367—~1.1kAutomated safety check: NotesGPL-3.0
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 3 days ago
    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 today
    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.

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

More from haumacher/phoneblock

  • Cleanup Workspace

    haumacher/phoneblock

    Park a finished worktree — commit real work, delete temporary/generated leftovers, then switch to the throwaway branch named after the workspace directory and reset it to origin/master.

    367 GitHub stars~1.1k tokensUpdated 6 days ago
    Auto-check: notes

  • Dongle Crash Analysis

    haumacher/phoneblock

    Decode and analyze an ESP32 dongle crash report (uploaded .coredump).

    367 GitHub stars~1.9k tokensUpdated 6 days ago
    Auto-check: notes

  • Diag Tuning

    haumacher/phoneblock

    Tune the PhoneBlock diagnostics log analysis — inspect aggregated log signatures, find noise / signature fragmentation / PII leaks, and propose, audit and promote scrub rules (and detection rules)…

    367 GitHub stars~2.1k tokensUpdated 6 days ago
    Auto-check passed

Works with

Categories

Questions about Fix Issue

What does Fix Issue do?

Start work on a GitHub issue — verify a clean workspace, read the issue, branch off the correct base (the branch where the fix will ship) as issue-<nr-<short-description, then plan the implementation. Fix Issue is an agent skill from haumacher/phoneblock. Start work on a GitHub issue — verify a clean workspace, read the issue, branch off the correct base (the branch where the fix will ship) as issue-<nr-<short-description, then plan the implementation.

When should I use Fix Issue?

Fix Issue fits situations like: the user says fix issue 123.

How do I install Fix Issue in Claude Code?

Run `npx skills add haumacher/phoneblock --skill fix-issue -a claude-code`. Or copy the skill folder (.claude/skills/fix-issue in haumacher/phoneblock) 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 haumacher/phoneblock --skill fix-issue -a codex`. Or copy the skill folder (.claude/skills/fix-issue in haumacher/phoneblock) 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 haumacher/phoneblock --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). Its frontmatter pre-approves these tools: Bash, Read, Glob, Grep, WebFetch.

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 notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Fix Issue use?

Fix Issue is published under the GPL-3.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 1.1k tokens (SKILL.md is roughly 4.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: 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?

haumacher (a GitHub user) maintains it in haumacher/phoneblock, which has 367 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 3, 2026.

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