Add an automated check

Turn an agreed rule into a check the whole team can run.

Fetch https://ntent.app/r/task/add-a-check.json and follow it. Stop and ask me at any step that says to, and do not decide something on my behalf that the plan says is mine to decide.

The steps

Here so you can follow along, or do it yourself. Your agent gets the same list from the plan above.

1. 01

   Choose a warning or a blocking check

   Ask: could anyone on the team fix this failure on their own laptop, offline, from a fresh copy of the repo? If yes, the check can stop the commit (a gate). If not, it should only print a warning (a nag).

   Success check: You can say "gate" or "nag" and give the reason.

2. 02

   Write the rule

   For code conventions, like no hand-typed colours, sizes, or text, write a lint rule. Lint is the tool that reads your code and flags problems.

   uses Design convention lint rules · eslint-rules.mjs

3. 03

   Prove it fires

   Make a small file that breaks the rule on purpose (a probe). Run the check and make sure it fails. Then run it on code that follows the rule and make sure it passes, so it does not cry wolf.

   uses Lint rule probes · check-probes.mjs

   Success check: Break the rule pattern on purpose and the probe check fails even though lint passes.

4. 04

   Introduce the rule gradually

   If lots of existing files already break the rule, start with a warning. Pick a date to fix them, and switch the rule to blocking on that date.

   uses Gradual rule rollout

5. 05

   Document the rule and its command

   In the project instructions file, write the rule with the command that checks it. If no script can check a rule, say a person has to.

   uses Shared project instructions · AGENTS.md