Guide · Agent skill
How to use the Resolve FIXME Comments agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The resolve-fixme skill is a set of instructions and a bundled shell script that tells a coding agent to find every FIXME comment in a project, read the full comment blocks, and implement the work they describe. It is aimed at maintainers and developers who have accumulated FIXME notes and want them actioned rather than left in the code. After this guide you will know what the skill does, how to install it, how to ask for it in plain language, and what it needs to run.
Resolve FIXME Commentstailcallhq/forgecode · Apache-2.0 Download the skill Quick start
- 1Get the skill folder. Download the ZIP from the skill's page on this directory and unzip it.
- 2Place it where the agent can read it. Unzip into ~/.claude/skills/ for personal use, or into the project's .claude/skills/ folder for one project. Alternatively, upload it under Settings → Capabilities → Skills in the Claude apps.
- 3Confirm the requirements. Make sure bash, ripgrep or grep with python3 are available, and that cargo and cargo-insta are installed if the project is Rust.
- 4Ask in plain language. Request that the agent fix, resolve, or address the FIXME comments, optionally naming a path to limit scope.
- 5Let the agent run the discovery script. The agent runs find-fixme.sh and reads the full comment block around each hit, not just the matching line.
- 6Review the grouped changes. Check that related FIXMEs spanning several files were implemented together and that comments were removed only where the work is complete.
- 7Confirm no FIXMEs remain. The agent runs cargo insta test --accept and re-runs the discovery script to confirm no FIXMEs remain in scope.
What an agent skill is and what this one does
An agent skill is a folder containing a SKILL.md file with instructions, plus optional supporting files such as scripts. When a request matches the skill's description, the agent follows its workflow. This skill's files are SKILL.md and scripts/find-fixme.sh.
When you ask the agent to fix or resolve FIXME comments, the skill has it run the discovery script to list each FIXME with nearby lines of code. The agent then reads the full comment block, since the FIXME line is often only the start of the instruction. Related FIXMEs spanning several files are grouped into one implementation task, and the agent makes the complete code changes the comments ask for. A FIXME is removed only after its work is done, and the search is re-run to confirm none remain.
Install the skill
You can install the skill in either of two ways. Download the ZIP from the skill's page on this directory and unzip it into ~/.claude/skills/ to make it available for your user account, or into a project's .claude/skills/ folder to make it available only in that project.
Alternatively, in the Claude apps, open Settings, go to Capabilities, and upload the skill under Skills.
- Personal install: unzip into ~/.claude/skills/
- Project install: unzip into the project's .claude/skills/ folder
- Claude apps: Settings → Capabilities → Skills, then upload
Check the requirements before you run it
The skill needs bash, plus either ripgrep (rg) or grep together with python3. The discovery script works with either search tool. The final verification step assumes a Rust project, because it runs cargo insta test --accept, so you need the Rust toolchain with cargo and cargo-insta installed.
The skill runs a script and does not use the network. The script skips .git/, target/, node_modules/, and vendor/ directories.
- bash
- ripgrep (rg) or grep and python3
- Rust toolchain with cargo and cargo-insta for the verification step
Run the discovery script yourself (optional)
The agent runs the script as part of the workflow, but you can run it from the repository root to see what it will find. The PATH argument is optional; leave it out to search the whole working directory. The script prints each FIXME with 2 lines of context before and 5 lines after, plus the file path and line number.
- PATH is optional; omit it to search the entire working directory
- Output includes 2 lines before and 5 lines after each FIXME
- Output includes exact file path and line number
bash .forge/skills/resolve-fixme/scripts/find-fixme.sh [PATH]Trigger the skill with natural requests
You do not need a special syntax. The skill's description says it applies when you ask to fix, resolve, or address FIXME comments, or when running the "fixme" command. Ask in plain language and name a folder if you want to limit the scope.
Be specific about scope when the project is large. The script accepts a path, so a request tied to one module is easier to review than one covering the whole repository.
- "Resolve the FIXME comments in this repo."
- "Address the FIXMEs under src/billing."
- "Fix all FIXMEs and check that none remain."
What to expect during a run
The agent follows five stages: run the discovery script, expand each hit into its full comment block, consolidate related FIXMEs across files, implement every one completely, and then verify. The skill states there is no skip path, so every FIXME it finds is attempted.
Because grouped FIXMEs are resolved together, a single change can touch several files. Review the diff as a whole rather than file by file.
What people use it for
- Clearing a backlog of FIXME notes in a Rust codebase that has built up over time.
- Carrying out a multi-file refactor that was described in scattered FIXME comments, such as introducing a new type and removing a parameter once it exists.
- Working through FIXMEs in one module by passing its path to the discovery script.
Frequently asked questions
How do I install the resolve-fixme skill?
Download the ZIP from the skill's page on this directory and unzip it into ~/.claude/skills/ for your user, or into a project's .claude/skills/ folder. In the Claude apps you can instead upload it under Settings → Capabilities → Skills.
What does the resolve-fixme skill require?
It requires bash and either ripgrep (rg) or grep with python3. The final verification step needs a Rust toolchain with cargo and cargo-insta, because it runs cargo insta test --accept.
Does the resolve-fixme skill use the internet?
No. The skill is listed as not using the network. It does run a bundled shell script, scripts/find-fixme.sh, which searches the project for FIXME markers.
Can the skill skip FIXMEs that are just informal reminders?
No. The skill has no skip path and will attempt every FIXME it finds. If your FIXMEs are notes that should not be acted on automatically, do not use this skill on that codebase.
Does it work on non-Rust projects?
The discovery script is generic, but the verification step assumes a Rust project with cargo insta. In a codebase that does not run cargo, that final check does not apply, so the skill is a poor fit.
Is there an alternative if I only want to list FIXMEs?
You can run the bundled find-fixme.sh script yourself from the repository root to see each FIXME with its file path, line number and surrounding lines, without letting the agent make changes. The source does not describe other tools for this.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you are a maintainer or developer with many FIXME notes, especially in a Rust project, and want an agent to implement them with grouped multi-file changes. Pick something else if your FIXMEs are informal reminders you do not want acted on, or if your project does not run cargo, since the skill has no skip path and its verification assumes Rust.
Download the skill