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

3. Consolidate related FIXMEs across files

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: