pre-commitlisted

# Skill — Pre-commit checkpoint > The checkpoint that must **re-measure rather than re-read**. The implementer's report of a green > recipe is a claim like any other, and the one thing a fresh context can do that the implementer > cannot is run it again without knowing what it is supposed to say. _(Part of the `checkpoints` ritual > pack — see [`../../README.md`](../../README.md) for the verdict vocabulary in full and for what this > pack cannot enforce.)_ ## When to use it Before committing **full-lane** work: the finished diff is graded, then committed. The adopting workspace's autonomy tiers do not move that moment — a tier says who must **attend** an action, and a workspace whose commits and pushes are unattended by policy has said no *person* waits on them, not that nothing is owed before them. An unattended commit is still committed after the verdict. If the moment was missed — work misjudged as triage, or committed before anyone called it finished — the verdict is owed before the work is put in front of anyone; which act does so first is for the adopting workspace's gates to say, and a pull request is the usual first one. That is the recovery for a missed moment, never an alternative moment. The lane boundary is likewise the adopting workspace's; see the session-open skill for why this pack does not set it. Also whenever a change touches doctrine, the autonomy tiers, or the platform floor — work whose blast radius is large even when no milestone or roadmap state m