resolve-fixme

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.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written, fully actionable workflow with concrete commands, explicit validation checkpoints, and a real referenced bundle script. It respects Claude's intelligence while giving exact, executable guidance end to end.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence—no explanation of what a FIXME is or how comments work—each sentence is directive ("Do not rely on the discovery output alone", "Resolve the whole task consistently"), matching the 'lean and efficient' anchor.	3 / 3
Actionability	Provides copy-paste-ready, executable commands: the discovery script invocation `bash .forge/skills/resolve-fixme/scripts/find-fixme.sh [PATH]` and verification `cargo insta test --accept`, plus concrete capture fields (file path, start/end line) for each hit.	3 / 3
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints—re-run the discovery script and 'Confirm that no FIXME comments remain'—and a feedback loop around the critical rule of not removing comments until work is done, matching the top anchor for sequence plus validation.	3 / 3
Progressive Disclosure	Well-organized sections present the overview inline and delegate the heavy lifting to one real, referenced bundle script (scripts/find-fixme.sh, which exists), keeping references one level deep and clearly signaled.	3 / 3
	Total	12 / 12 Passed

Description

85%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that explicitly pairs capabilities with 'Use when' triggers and concrete workflow steps. The only soft spot is trigger-term coverage, which is limited to a single FIXME keyword family.

Suggestions

Broaden trigger terms to cover phrasings a user might actually say, e.g. 'use when the user wants to clean up TODOs/FIXMEs, finish incomplete code marked with FIXME, or asks what FIXME comments are left'.

Consider mentioning the verification outcome as a trigger benefit (e.g. 'confirms no FIXMEs remain') to help it surface when users want a completeness check.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—"Find all FIXME comments", "expands multiline comment blocks", "groups related FIXMEs across files", "completes the full underlying code changes", "removes the FIXME comments only after the work is done", "verifies that no FIXMEs remain"—matching the top anchor for several specific actions.	3 / 3
Completeness	Clearly answers what (the full action chain) and when via the explicit "Use when the user asks to fix, resolve, or address FIXME comments, or when running the 'fixme' command" clause, matching the top anchor for both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	Includes the trigger family "fix, resolve, or address FIXME comments" plus the "fixme" command, but the natural-keyword coverage is narrow (single FIXME keyword family) and lacks common phrasings users might say, so it sits at 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The FIXME-comment niche is distinct and the triggers ("FIXME comments", "fixme" command) are unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tailcallhq/forgecode
Path: .forge/skills/resolve-fixme/SKILL.md
Commit: 1ca089a

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.