Know what “done” actually means.
Read verification evidence, ask for a useful review, and handle a failed check without hiding it.
An agent can sound certain before it has enough evidence. I care more about a specific result than a confident summary. “The empty state appears at this route with zero records” tells you something. “Everything looks production-ready” doesn’t tell you much.
Match each claim to a check.
Type checks help with types. Unit tests help with the behavior they exercise. A browser check helps with an affected user flow. A provider fake helps establish local handling, but it doesn’t establish that a real email arrived.
Read the report with those limits in mind. Ask which checks ran and which acceptance criteria they cover. A screenshot can show layout; it can’t prove that an API rejects another user’s resource ID.
› Show the checks that ran for this change, their actual results, and which acceptance criteria each covers. Separate failures, skipped checks, and checks that could not run.Use a focused verification pass.
verify-work starts from the impact of the diff and traces affected consumers. That is more useful than choosing checks because the repository happens to contain a frontend or database.
Install it if it isn’t available. Then give it the original request, a base ref if needed, and any results already collected. It may add missing tests, but it doesn’t patch product code.
$ npx skills add akdevsaha-dev/factory-skills --skill verify-work review-changes› /verify-work verify this change against main and the task’s acceptance criteria. Use existing test tooling. Include affected runtime paths and explain anything that could not be checked.Ask for a review that can disagree.
Give the reviewer the intended behavior and the change, rather than a persuasive explanation of why the implementation is correct. Useful findings identify a location and a concrete failure scenario.
review-changes reports defects and a verdict. Fix confirmed findings through an implementation step, then recheck the paths affected by those fixes.
› /review-changes review this branch against main and the original request. Read the callers of changed interfaces. Report concrete failures with locations, and mark any unresolved assumptions.Keep a failed check visible.
If the environment is missing credentials, the relevant provider check is unverified. If a test failed before your edit, establish that baseline before attributing it to the change. If your edit caused the failure, fix it and rerun the affected check.
You don’t need to rerun everything after every sentence change. You do need fresh evidence when you change the code that earlier evidence covered. Keep the distinction clear in the handoff.
› Investigate this failed check before changing more code. Show whether it exists on the baseline or was introduced by the current diff. Then propose the smallest fix.