resolve-fixme

Finds all FIXME comments in a codebase and implements the work they describe.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/swcstudiospace/aimeecodes --skill resolve-fixme-swcstudiospace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-fixme
Source: https://github.com/swcstudiospace/aimeecodes/tree/main/.aimee/skills/resolve-fixme
Command: npx skills add https://github.com/swcstudiospace/aimeecodes --skill resolve-fixme-swcstudiospace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? FIXME comments accumulate in codebases as reminders of unfinished work, but they are easy to ignore and often describe multi-file changes that are tedious to track down and complete manually. This Skill discovers every FIXME, expands multiline comment blocks into full instructions, groups related items across files, and implements the underlying code changes. ## Core Features & Use Cases - Codebase-wide discovery: Runs a shell script that locates every FIXME with surrounding context, skipping .git, target, node_modules, and vendor directories. - Cross-file consolidation: Groups related FIXMEs that describe facets of one larger task into a single coherent implementation plan. - Complete implementation with verification: Finishes the actual code changes, removes comments only after the work is done, runs the project test suite, and re-scans to confirm no FIXMEs remain. - Use Case: Before a release, ask the agent to resolve all outstanding FIXMEs; it finds a type refactor hinted at in three different files, implements the new type, updates the service and UI layers, and verifies with cargo insta test. ## Quick Start Ask the agent to find and resolve all FIXME comments in the repository, implementing the work each one describes.

Frequently Asked Questions about resolve-fixme

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find and fix all FIXME comments in a codebase?▼

Run the find-fixme.sh discovery script from the repository root to list every FIXME with file path, line number, and surrounding context. Then expand each comment block, group related items, implement the described changes, and re-run the script to confirm none remain.

How to handle FIXME comments that span multiple files?▼

Read all expanded FIXMEs together before editing and group those sharing vocabulary, types, or services into one task. Implement the whole group consistently across files rather than resolving each comment in isolation.

Does the FIXME discovery script require ripgrep?▼

Ripgrep is preferred but not required. The script falls back to grep combined with python3 for parsing when rg is unavailable, and it skips .git, target, node_modules, and vendor directories in both modes.

Can I search only part of the repository for FIXMEs?▼

Yes, pass an optional PATH argument to the find-fixme.sh script to limit the search scope. Omitting the argument searches the entire current working directory.

When should a FIXME comment be removed from the code?▼

Remove a FIXME only after the work it describes is fully implemented and verified. Deleting the comment before completing the underlying change loses the record of required work and is treated as a failure.