About full-stop
Trigger only when the user or another skill explicitly invokes this skill
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ sztadii/ agent-skills --skill full-stopAfter installing, type/full-stopin Claude Code to confirm it loaded.
Bundled filesagents/openai.yaml
Details
From the project READMEFull Stop
Scope
Implement a change, simplify, verify and review it once, then publish it as a PR. Invocation authorizes implementation, local setup, verification, independent review, task commits/pushes and PR publication. Publication ends this workflow; do not maintain, merge or deploy the PR.
Honor narrower constraints such as “do not push”. Resolve routine choices without phase approvals. Escalate only blocking product decisions, access problems or out-of-scope actions, after finishing independent work.
All commits and pushes must use commit-push through file-pr. Do not run separate commit/push commands outside that workflow.
Dependencies
Required: $simplify, $proof, $council, $file-pr and $commit-push.
Before starting, find each required skill in the agent's catalog or installed locations, read its SKILL.md and complete its dependency check. Repository links alone are insufficient. If any skill is missing or unreadable, stop this workflow and its caller; name the affected skills without substituting or installing.
Workflow
Deliver
- Infer acceptance criteria, scope, actual base and destination from context and repository instructions. Reuse the matching task branch/PR; preserve unrelated changes. Do not require tickets or update issue trackers.
- Implement the complete change, meaningful regression coverage and required documentation. Inspect the whole diff for readability and incidental churn; keep tests proportional to risk. Avoid redesigns.
- Invoke
$simplifyonce on the complete local task diff with the check scope below. Retain its changes and verification result; a no-op is valid. Stop on failed or incomplete verification. - Start
$councilonce on the simplified snapshot with intent,$simplifyresults and user-selected reviewers or settings. While reviewers work, invoke$proofon the same snapshot with acceptance criteria and the check scope below; give$councilthe$proofresult before it synthesizes findings. Keep the reviewed snapshot stable until reviewers finish. - Fix substantiated
$councilfindings and in-scope$prooffailures, then rerun$prooffor the affected checks. Never start another$councilround; record these fixes as not council-reviewed. Unfixed findings and failed or incomplete verification leave delivery incomplete; report them. - Invoke
$file-prwith prepared changes, matching PR, constraints, findings and useful evidence with its snapshot. Use its publication result.
Check scope
$simplifyand$proofrun checks only for changed files and code that depends on them: lint those files, run related tests (for examplevitest relatedorjest --findRelatedTests) and typecheck as narrowly as the tooling allows. Avoid whole-suite commands such asnpm test; the PR CI runs full checks.
Pass scope, permissions, revision and evidence between skills. Preserve each skill's returned state, evidence and blockers; do not bypass blockers or repeat child actions.
Result
Report delivered behavior, evidence, $council verdict, fixes made after it,
PR URL, published head and draft status; report pending CI as pending.
Distinguish failed, unverified and deferred requirements. Do not invent success.