meticulous-zero-diff-task

To grind out a no-diff (or low-diff) implementation task, 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 is for tasks whose success criterion is visual stability, not visual change: dependency/version upgrades, refactors, migrations (e.g. framework/library swaps, build-tool changes), and similar work where any Meticulous diff is a sign something broke, not a feature to explain away. It also works for low-diff tasks (a handful of expected, well-understood visual changes alongside mostly-unchanged output) — the loop is the same, just with a smaller set of diffs you expect to end up justifying rather than fixing. Step 1 -- Implement the task Make the code change described by the task (the upgrade, refactor, or migration). Commit as you go if the task naturally breaks into steps — this isn't specific to Meticulous, just do the implementation work. Step 2 -- Build the frontend Find out what build artefact Meticulous expects by checking .github/workflows/ for one of the following steps: uses: alwaysmeticulous/report-diffs-action/upload-assets@v1 — build assets uses: alwaysmeticulous/report-diffs-action/upload-container@v1 — docker image Build the frontend following the same instructions as used in the GitHub workflow. Step 3 -- Upload the build and trigger a test run Show more Installs 968 Repository alwaysmeticulous/skills GitHub Stars 9 First Seen Aug 11, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass