1---
2name: full-stop
3description: Trigger this if the user says 'full stop', even as a closing "Full stop." that reads like emphasis.
4---
5
6# Full Stop
7
8Do the same work as `full-send`, but stop with the PR ready for the user to merge.
9Never merge it.
10
11Read [full-send](../full-send/SKILL.md) and follow its workflow, proof rules,
12review, and babysitting steps. An explicit "full stop" request authorizes that
13work without a separate "full send" request. That includes full-send's
14testing permission. A "full stop" request is the permission for the test
15methods Proof needs, even when a project file says to ask first, for
16example before computer use. Use those methods directly. Its merge
17permission does not apply. The overrides below take precedence.
18
19## No merging
20
21You may commit, push, rebase, and fix conflicts on this task's branch under
22[file-pr's push policy](../file-pr/SKILL.md#push-permission). Never merge,
23enable auto-merge, enter a merge queue, push to the default branch, bypass
24branch protection, or delegate those actions.
25
26Disable existing auto-merge and remove the PR from any merge queue before
27work begins; check again before each push. Report these changes. If you
28cannot prevent automatic merging, report the blocker before proceeding.
29
30## Stop at the gate
31
32Use full-send's merge gate as the readiness check. Replace its merge and
33final report steps with a handoff. Proof and review must cover the final diff;
34recheck behavior changes and meaningful conflict fixes before handoff.
35
36Fetch the target branch and check the live PR's head, base, checks, reviews,
37and mergeability. Confirm it is open, not a draft, and not set to merge
38without the user. If someone else merged it, report that instead.
39
40- **Ready to merge:** the merge gate passes. Leave the PR open and unmerged.
41- **Waiting for required approval:** only human approval remains. Confirm
42 that this is the actual blocker.
43- **Blocked:** explain what prevents readiness, what you tried, and what is
44 needed. Follow full-send's rules for asking the user.
45
46In T3 Code, call `unwatch_pull_request` before the handoff or a question.
47Report the PR link, final head, verdict, proof, reviewer outcome, and remaining
48risks. State whether the PR is still open and unmerged.