Agent skill · alwaysmeticulous
meticulous-fix
Fix the visual diffs that have been reviewed and rejected on a Meticulous test run, following their review comments if given. Use when a user has reviewed the results of a test run and is handing off to an agent to implement the fixes.
What it needs
About 5k tokens when loaded.
What this skill does
To fix diffs that have already been reviewed and rejected, follow the workflow below step by step, using the CLI or MCP commands as described. Before starting, run the meticulous-cli-update skill to ensure the Meticulous CLI and skills are up to date — unless it has already run earlier in this conversation, in which case skip it. This skill assumes the review has already happened — a user (or the meticulous-review skill) has gone through the run and rejected the diffs that are real problems, possibly leaving comments explaining what's wrong or what to do about it, though comments aren't a given. Your job here is narrower than a full review: don't re-litigate diffs that weren't rejected, and don't second-guess the rejection itself — just work out what needs to change and make it happen. Step 1 -- Get the rejected diffs and any commented-on diffs Important — these --only flags are additive (OR'd): passing both --onlyRejected and --onlyWithComments returns every diff that's rejected, has an open comment, or both — not just the intersection — since a comment on a diff that wasn't formally rejected may still contain an instruction worth acting on. --includeAllDiffs is implied, so this spans the full run rather than just the selected subset; --includeReviews adds decision/openComments columns so you can tell which case each row is. Not every commented row is a fix target. The meticulous-review skill's ignore-diff posts a note saying the diff is unrelated to the change and leaves it unreviewed — that comment is not a fix instruction. When reading Step 1's rows, skip diffs whose only open comments are those; leave those threads alone. Step 2 -- Read the review comments for diffs that have any For each diff with openComments > 0: This is your primary source of instructions — a comment usually says what's wrong and, often, what to do about it. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alwaysmeticulous/meticulous-fix