← ClaudeAtlas

full-stoplisted

Use when the user invokes `$full-stop` to finish work end-to-end and stop with the PR ready for their own merge.
RIJUDEVx/agent-skills · ★ 1 · AI & Automation · score 77
Install: claude install-skill RIJUDEVx/agent-skills
# Full Stop Do the same work as `$full-send`, but stop with the PR ready for the user to merge. Never merge it. Read [full-send](/Users/home/.agents/skills/full-send/SKILL.md) at that absolute path and follow its stages, proof rules, review loop, review rules, watching, merge gate, comment format, and asking rules. If that file is not readable, stop and report it. Do not guess its contents. An explicit `$full-stop` request authorizes that work without a separate `$full-send` request. That includes full-send's testing permission. A `$full-stop` request is the permission for the test methods Proof needs, even when a project file says to ask first, for example before computer use. Use those methods directly. **Full-send's merge authority does NOT apply.** The grant to merge, the merge step, and any "merge with the method the repo allows" instruction are not permissions for this task. The overrides below take precedence. ## No merging You may commit, push, rebase, fix conflicts, and use `--force-with-lease` on this task's branch. Never merge, enable auto-merge, enter a merge queue, push to the default branch, bypass branch protection, or delegate those actions. Disable existing auto-merge and remove the PR from any merge queue before work begins; check again before each push. Report these changes. If you cannot prevent automatic merging, report the blocker before proceeding. ## Stop at the gate Use full-send's merge gate as the readiness check. Replace its merge and fina