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

FIXME Resolver

by tailcallhq in tailcallhq/forgecode

Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.

Apache-2.0Auto-check passedDevelopment

Install FIXME Resolver

skills CLI
$ npx skills add tailcallhq/forgecode --skill resolve-fixme -a claude-code

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

GitHub CLI
$ gh skill install tailcallhq/forgecode resolve-fixme --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/tailcallhq/forgecode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.forge/skills/resolve-fixme .claude/skills/resolve-fixme && 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
resolve-fixme
GitHub stars
7.6k
Token cost
~1.1k tokens
SKILL.md length
585 words
Files
2 (incl. scripts)
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.

  • Works in 5 steps: Run the discovery script → Expand each FIXME into its full… → Consolidate related FIXMEs across files → …
  • Resolving all FIXME comments in a repository
  • SKILL.md covers Workflow and Notes
  • Runs Shell scripts from its folder; calls bash and cargo

What it does

The agent runs scripts/find-fixme.sh, which prints each FIXME with 2 lines of context before and 5 after, plus the file path and line number, and skips .git, target, node_modules and vendor. An optional path narrows the search, and the script needs either ripgrep or grep with python3.

The agent then opens each hit and expands it to the whole comment block, since the real instruction often continues on later lines. FIXMEs that describe parts of one change, such as a new type in one file and a parameter to drop in another, are grouped into one task and resolved together in a sensible order. Every FIXME must be fully implemented, with no skip path, the comments are removed only after the work is finished, and a final check confirms none remain.

When your agent uses it

  • Resolving all FIXME comments in a repository
  • Addressing FIXMEs that describe a refactor spread over several files
  • Verifying that no FIXMEs remain before a release

Example prompts

  • “Resolve all the FIXME comments in the src directory.”
  • “Run the fixme command and implement everything the comments ask for.”
  • “Check that no FIXMEs are left after the refactor.”

Requirements

  • bash
  • ripgrep, or grep together with python3

Workflow steps

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

  1. Run the discovery script
  2. Expand each FIXME into its full instruction
  3. Consolidate related FIXMEs across files
  4. Implement every FIXME completely
  5. Verify

What it can do on your machine

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

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash
    • cargo

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

  • Network

    No URLs in SKILL.md.

    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

FIXME Resolver loads about 1.1k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 585 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~123
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 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); the scripts in this folder are not scanned.

SKILL.md

The full file from tailcallhq/forgecode at commit a7ff952, republished under its Apache-2.0 licence (© tailcallhq). 585 words, ~1,124 tokens.

Download SKILL.mdSave it as .claude/skills/resolve-fixme/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
resolve-fixme
description
Find all FIXME comments across the codebase and fully implement the work they describe. Use when the user asks to fix, resolve, or address FIXME comments, or when running the "fixme" command. Runs a discovery script to find every FIXME, expands multiline comment blocks, groups related FIXMEs across files into a single implementation task, completes the full underlying code changes, removes the FIXME comments only after the work is done, and verifies that no FIXMEs remain.

Resolve FIXME Comments

Workflow

1. Run the discovery script

Execute the script from the repository root to collect all FIXMEs with context:

bash .forge/skills/resolve-fixme/scripts/find-fixme.sh [PATH]
  • PATH is optional; omit it to search the entire working directory.
  • The script prints each FIXME with 2 lines of context before and 5 lines after, along with the exact file path and line number.
  • Skips .git/, target/, node_modules/, and vendor/.
  • Requires either rg (ripgrep) or grep + python3.
2. Expand each FIXME into its full instruction

Do not rely on the discovery output alone.

For every hit:

  1. Open the file and read around the reported line.
  2. Expand the FIXME to include the entire comment block.
  3. Treat all consecutive related comment lines as part of the same instruction.

Important:

  • A FIXME may be multiline. The line containing FIXME is often only the beginning.
  • The real instruction may continue on following comment lines and may contain the actual implementation details.
  • Do not interpret or edit a FIXME until you have read the full block.

For each expanded FIXME, capture:

  • file path
  • start line and end line of the full comment block
  • a short summary of what that FIXME is asking for

Before editing code, review all expanded FIXMEs together.

Many FIXMEs describe different facets of the same underlying task across multiple files. For example:

  • one file may describe a domain type that needs to be introduced
  • another may describe a parameter that should disappear once that type exists
  • another may describe a service, repo, or UI update needed to complete the same refactor

Group such FIXMEs into a single implementation task.

When grouping, look for:

  • shared vocabulary
  • references to the same type, service, repo, parameter, or feature
  • comments that clearly describe prerequisite and follow-up changes in different files
  • comments that only make sense when read together

For each group, produce one consolidated understanding of the task:

  • all files and line ranges involved
  • the complete implementation required across the group
  • the order in which the changes should be made

Do not resolve grouped FIXMEs one file at a time in isolation. Resolve the whole task consistently.

Show full SKILL.md (231 more words)Show less
4. Implement every FIXME completely

Every FIXME must be resolved. There is no skip path.

Work through each grouped task until the underlying implementation is complete:

  1. Read any additional files needed to understand the design.
  2. Create or modify the required code, types, services, repos, tests, configs, or templates.
  3. Propagate the change through every affected file in the group.
  4. Remove each FIXME comment only after the work it describes has actually been implemented.

Critical rule: Never delete or rewrite a FIXME comment unless the underlying implementation is finished. The comment is a record of required work. Removing it before completing that work is a failure.

If the FIXME implies a larger refactor, do the refactor. If it requires creating new supporting code, create it. Do not stop at the first local change if the comment clearly implies additional follow-through elsewhere.

5. Verify

After resolving all FIXMEs:

  1. Run the project's standard verification step:
sh
cargo insta test --accept
  1. Re-run the discovery script:
sh
bash .forge/skills/resolve-fixme/scripts/find-fixme.sh [PATH]
  1. Confirm that no FIXME comments remain in the targeted scope.

Notes

  • Prefer targeted fixes, but do not under-scope the work when multiple FIXMEs describe one larger task.
  • Read broadly before editing when the intent is ambiguous.
  • Consistency matters more than locality: grouped FIXMEs should lead to one coherent implementation.
  • The job is not to clean up comments. The job is to complete the implementation those comments are pointing at.

© tailcallhq, 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

SKILL.md and 1 other file (scripts) in .forge/skills/resolve-fixme of tailcallhq/forgecode.

  • SKILL.md
  • scripts/find-fixme.sh

Open the folder on GitHubat commit a7ff952

Compare with similar skills

FIXME Resolver 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.

FIXME Resolver compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
FIXME Resolver this skilltailcallhq/forgecode7.6k—~1.1kAutomated safety check: PassApache-2.0
Systematic Code Refactoringluongnv89/claude-howto42k—~3kAutomated safety check: PassMIT
Code Refactoring Workflowluongnv89/claude-howto42k—~3.1kAutomated safety check: PassMIT
DesloppifyGit-on-my-level/codex-autorunner875—~3.4kAutomated safety check: PassMIT
Tech Debt Analyzerailabs-393/ai-labs-claude-skills4541 repos~3.9kAutomated safety check: PassMIT
Code Quality Gatefengshao1227/ccg-workflow5.9k—~593Automated safety check: NotesMIT

Similar skills

  • Systematic Code Refactoring

    luongnv89/claude-howto

    Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.

    42k GitHub stars~3k tokensUpdated 9 days ago
    DevelopmentAuto-check passed

  • Code Refactoring Workflow

    luongnv89/claude-howto

    Guides systematic, test-backed refactoring in the style of Martin Fowler, moving through research, planning and small incremental changes with your approval at each phase.

    42k GitHub stars~3.1k tokensUpdated 9 days ago
    DevelopmentAuto-check passed

  • Desloppify

    Git-on-my-level/codex-autorunner

    Codebase health scanner and technical debt tracker. An agent skill from Git-on-my-level/codex-autorunner.

    875 GitHub stars~3.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Tech Debt Analyzer

    ailabs-393/ai-labs-claude-skills

    This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability.

    454 GitHub starsUsed in 1 repo~3.9k tokens
    DevelopmentAuto-check passed

  • Code Quality Gate

    fengshao1227/ccg-workflow

    Scans code for complexity, long functions, duplicated blocks, naming problems and code smells with a Node script, then reports and suggests refactors.

    5.9k GitHub stars~593 tokensUpdated 24 days ago
    DevelopmentAuto-check: notes

  • Smell Check

    Zhen-Bo/smell-check

    Runs a smell-first audit on a user-chosen path set: measures structure metrics, applies a named size profile, and reports code smells and test smells with evidence strength.

    240 GitHub stars~1.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from tailcallhq/forgecode

All 14 skills in this repo

  • Git Merge Conflict Resolver

    tailcallhq/forgecode

    Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.

    7.6k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed

  • Forge CLI Debug Workflow

    tailcallhq/forgecode

    Gives a systematic process for debugging the forge CLI: build in debug mode, check the latest help output, test with the non-interactive -p flag, and clone conversations before reproducing bugs.

    7.6k GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

  • Reasoning Serialization Tests

    tailcallhq/forgecode

    Checks that ReasoningConfig fields are serialized into the right provider-specific JSON for OpenRouter, Anthropic, GitHub Copilot and Codex requests.

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

  • Implementation Plan Creator

    tailcallhq/forgecode

    Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.

    7.6k GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed

  • Release Notes Writer

    tailcallhq/forgecode

    Pulls a GitHub release and every linked pull request, then writes polished, factual release notes from the combined set of changes.

    7.6k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

  • Skill Creation Guide

    tailcallhq/forgecode

    Guidance for creating and updating agent skills: what skills provide, keeping context lean, choosing how specific to be, and how SKILL.md and bundled resources are laid out.

    7.6k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about FIXME Resolver

What does FIXME Resolver do?

Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done. git, target, node_modules and vendor. An optional path narrows the search, and the script needs either ripgrep or grep with python3.

When should I use FIXME Resolver?

FIXME Resolver fits situations like: resolving all FIXME comments in a repository; addressing FIXMEs that describe a refactor spread over several files; verifying that no FIXMEs remain before a release.

How do I install FIXME Resolver in Claude Code?

Run `npx skills add tailcallhq/forgecode --skill resolve-fixme -a claude-code`. Or copy the skill folder (.forge/skills/resolve-fixme in tailcallhq/forgecode) into .claude/skills/resolve-fixme in your project. Claude Code loads it when a task matches its description.

How do I install FIXME Resolver in Codex?

Run `npx skills add tailcallhq/forgecode --skill resolve-fixme -a codex`. Or copy the skill folder (.forge/skills/resolve-fixme in tailcallhq/forgecode) into .agents/skills/resolve-fixme in your project. Codex loads it when a task matches its description.

Can I use FIXME Resolver 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 tailcallhq/forgecode --skill resolve-fixme -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/resolve-fixme, .gemini/skills/resolve-fixme, .github/skills/resolve-fixme and .opencode/skills/resolve-fixme in your project.

What does FIXME Resolver need to run?

Going by SKILL.md and its folder, FIXME Resolver needs a shell for the scripts in its folder and the command-line tools its instructions call (bash and cargo). Our summary lists: bash; ripgrep, or grep together with python3.

Does FIXME Resolver access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is FIXME Resolver 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does FIXME Resolver use?

FIXME Resolver 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 FIXME Resolver use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 FIXME Resolver?

Skills that share tags, products or a category with FIXME Resolver: Systematic Code Refactoring (luongnv89/claude-howto, 42k stars), Code Refactoring Workflow (luongnv89/claude-howto, 42k stars), Desloppify (Git-on-my-level/codex-autorunner, 875 stars) and Tech Debt Analyzer (ailabs-393/ai-labs-claude-skills, 454 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains FIXME Resolver?

tailcallhq (a GitHub organization) maintains it in tailcallhq/forgecode, which has 7,641 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 2026.

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