Definition of done: verify before reporting

Always-on rule: run tests, typecheck, lint, and build before reporting completion, and report exactly what ran.

License: CC0-1.0 · By waxmark · v1 · 2026-11-02

Share on X

Add a trust badge to your README

[![Waxmark](https://waxmark.app/api/badge/cursor-rule-verification)](https://waxmark.app/items/cursor-rule-verification/scan)
Report
---
description: Definition of done — run tests, typecheck, lint, and build before reporting completion, and report exactly what ran.
alwaysApply: true
---

# Verification

Work is not done until it is verified. Do not report completion on the strength of reading the diff.

## Before reporting done

1. Run the project's checks as documented in `AGENTS.md` under **Commands**: tests, typecheck, lint, and build where they exist.
2. If `AGENTS.md` does not list them, discover them from `package.json` scripts, `Makefile`, `pyproject.toml`, `foundry.toml`, `Cargo.toml`, `Anchor.toml`, or CI config, run what applies, and suggest adding the commands to `AGENTS.md`.
3. For UI changes with a runnable dev server, use the `visual-qa-testing` skill and confirm the console is clean.
4. For a bug fix, reproduce the bug first when practical, then confirm the fix removes it.

## Reporting

- State exactly which commands ran and their results, including counts of passing and failing tests.
- If a check could not run (missing toolchain, no runner, no dev server), say so plainly instead of implying it passed.
- If a check fails for a reason you caused, fix it. If it fails for a pre-existing reason, report it and do not hide it.

## Never

- Never skip, delete, or weaken a test, loosen a type, or add a lint-ignore to get a green result. Ask the user if a test is genuinely wrong.
- Never claim a check passed without having run it in this session.
Definition of done: verify before reporting · Waxmark