Guardrails Check

Skill

Checks a planned or finished change against your written rules — persistence, data model, new technology, testing, destructive actions and git hygiene — and reports PASS or the exact gate that applies.

Best for

A quick check before starting significant work
A last check before declaring work done
Teams with a written rules file that people forget

What you give it

The change or plan
Your rules file

What you get back

PASS, or the specific rule that applies and what to do about it

How it works

Reads your rules file (the quick reference first, then the relevant sections).
Checks persistence, data model, technology, root-cause fixing, tests, destructive actions and git hygiene.
Reports PASS or the gate; suggests the Change Reviewer agent for a full diff review.

Example

You: /guardrails-check we will cache the cart in memory

Result: Gate: persistence. A cart held only in memory is lost on restart. Persist it in the database (cache is fine for speed, not as the source of truth).

Limits — please read

It enforces only what you have written.
It is a checklist, not a full review.