full-stop
Skill1 starsChanged 3 days agoMITView on GitHub
Use when the user invokes `$full-stop` to finish work end-to-end and stop with the PR ready for their own merge.
17 other projects use a version of this, 11 of them edited.
Adopted by
Most recently taken up by
- cogine-ai/cogine-dev-skillsetedited, first seen Nov 16, 2026
- mjeffrey18/skillstheir own version, first seen Nov 15, 2026
- lihbr/skillsedited, first seen Nov 15, 2026
- adelrodriguez/skillsedited, first seen Nov 15, 2026
- lbussell/agent-skillsedited, first seen Nov 8, 2026
- scottwater/skillsedited, first seen Nov 8, 2026
Used with
Projects with it also use leaving-pr-comments, sol-loop and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
scottwaterSkillleaving-pr-comments
Format comments an agent posts on GitHub on the user's behalf. Use whenever leaving a PR comment, review comment, or reply.
Also in 9 projects that use this
scottwaterSkillsol-loop
Review a change with GPT Sol in a loop until both agents agree. Use when the user says sol loop, or when another skill asks for a Sol review.
Also in 8 projects that use this
assisjpSkilltakeover
Take over an existing branch, pull request, worktree, or agent handoff while preserving the original goal, contributor credit, and concurrent work. Use when the user asks to take over, finish, rescue, or continue someone else's implementation. Do not use to replace a clear request to start new work.
Also in 4 projects that use this
assisjpSkillfile-pr
Prepare and open or update an authorized pull request with a concise problem-first description and verifiable evidence. Use when the user asks to create, file, open, or update a PR. Do not use merely to review a diff or when publication is not authorized.
Also in 8 projects that use this
owidSkillbabysit-pr
Spawn a background agent that babysits an open PR — triggers a Codex review, watches CI, judges and fixes valid findings, replies to and resolves review threads, and loops to a cap. Never merges. Trigger when the user asks to "babysit the PR", "ask for codex review(s) and watch CI", or after pushing a substantial chunk to a PR branch.
Also in 9 projects that use this
MicrosoftSkillcouncil
Convene the persona panel — six orthogonal review lenses — on a target. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.
Also in 6 projects that use this
- +1 more from scottwater
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 11
- t3dotgg/tstack★ 3.8k83% same
- cogine-ai/cogine-dev-skillset★ 386% same
- connorch/skills★ 283% same
- scottwater/skills★ 275% same
- adelrodriguez/skills★ 114% same
- johnnygreco/skills★ 185% same
- salasebas/skills★ 184% same
- lbussell/agent-skills★ 081% same
- lihbr/skills★ 083% same
- luisgui1757/sentinel★ 078% same
1 more not listed
Wrote their own version · 6
- Dhruv2mars/skills★ 3same name
- mneves75/skills★ 3same name
- JeffreyFerreiras/ai-skills★ 1same name
- Nexus-Organization-Infosec/ClaudeSkills★ 1same name
- ayv4zyan/skills★ 0same name
- mjeffrey18/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- analyze-logsSkill
- architectSkill
- build-audit-logsSkill
- cloudflareSkill
- code-reviewSkill
- design-engineeringSkill
- diagnosing-bugsSkill
- full-sendSkill
- ghSkill
- grillingSkill
- impeccableSkill
- improve-animationsSkill
- interrogateSkill
- no-use-effectSkill
- prSkill
- retroSkill
- t3-toolsSkill
- triageSkill
- unslopSkill
- vitestSkill
- wait-whatSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 1 is common, 2 are distinctive, and 1 is very specific to this project.
1
Common
Most of the 17 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 9
Do the same work as $full-send, but stop with the PR ready for the user to merge.
- Distinctive: line 12
Read full-send at that absolute path and follow its stages, proof rules, review loop, review rules, watching, merge gate, comment format, …
- Distinctive: line 39
Use full-send's merge gate as the readiness check.
- Common: line 48
Waiting for required approval: only human approval remains.
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 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 final report steps with a handoff. Proof and review must cover the final diff; recheck behavior changes and meaningful conflict fixes before the handoff.
Fetch the target branch and check the live PR's head, base, checks, reviews, and mergeability. Confirm it is open, not a draft, and not set to merge without the user. If someone else merged it, report that instead.
- Ready to merge: the merge gate passes. Leave the PR open and unmerged.
- Waiting for required approval: only human approval remains. Confirm that this is the actual blocker. Name the required approver if the repo specifies one.
- Blocked: explain what prevents readiness, what you tried, and what is needed. Follow full-send's rules for asking the user.
In T3 Code, call unwatch_pull_request before the handoff or a question. Report
the route and why, the stage ledger, the PR link, final head, verdict, proof, reviewer outcome, and
remaining risks.
State whether the PR is still open and unmerged.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

