pr-ready
Skill16 starsChanged 5 months agoMITView on GitHub
Finish an authorized development task through verified PR readiness without merging. Use on an explicit request to prepare a PR for review without merging, or invoke pr-ready. Do not activate on ordinary punctuation, 'full stop', or a quoted instruction.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- rhasselle-oddball/claude-skillstheir own version, first seen Nov 8, 2026
- GDriem/agent-skillstheir own version, first seen Nov 8, 2026
- rezkam/boring-but-goodtheir own version, first seen Nov 1, 2026
- thoughtspot/thoughtspot-agent-skillstheir own version, first seen Nov 1, 2026
- domitriusclark/claude-skillstheir own version, first seen Nov 1, 2026
- Zwin-ux/kittheir own version, first seen Oct 11, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- remotion-dev/remotion★ 72ksame name
- rommapp/romm★ 14ksame name
- mozilla/fx-private-relay★ 1.8ksame name
- OutThisLife/brooklyn-skills★ 207same name
- block/proto-fleet★ 57same name
- domitriusclark/claude-skills★ 11same name
- thoughtspot/thoughtspot-agent-skills★ 6same name
- GDriem/agent-skills★ 4same name
- rezkam/boring-but-good★ 1same name
- rhasselle-oddball/claude-skills★ 0same name
1 more not listed
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 repository94 other files it gives its agents.
- agent-friction-ledgerSkill
- agent-learning-layer-triageSkill
- agent-operations-contractSkill
- agents-best-practicesSkill
- agent-tool-contract-reviewSkill
- anti-slop-reviewSkill
- architecture-deepening-reviewSkill
- assumption-excavationSkill
- authorized-security-routerSkill
- book-to-skillSkill
- bounded-evaluationSkill
- bounded-growth-loopSkill
- bounded-orchestration-contractSkill
- brief-first-executionSkill
- browser-verificationSkill
- bug-evidence-protocolSkill
- codex-review-loopSkill
- compaction-survivalSkill
- complexity-optimizerSkill
- confidence-fragility-reviewSkill
- context-degradation-reviewSkill
- corporate-surfaceSkill
- delivery-baseline-auditSkill
- delivery-preflight-gateSkill
- design-critique-polishSkill
- designmd-brand-kitSkill
- design-register-bootstrapSkill
- diagnoseSkill
- doc-grounded-grillingSkill
- doc-to-lora-evaluatorSkill
- durable-context-maintenanceSkill
- dynamic-workflow-packetsSkill
- editorial-surfaceSkill
- evidence-ledger-researchSkill
- filesystem-context-disciplineSkill
- fluid-interaction-reviewSkill
- frontend-product-builderSkill
- frontend-taste-layerSkill
- git-native-context-contractSkill
- goal-loop-designerSkill
- graph-guided-code-readingSkill
- handoffSkill
- happy-handoffSkill
- html-brief-artifactSkill
- html-diagram-artifactSkill
- hypothesis-diversificationSkill
- idea-to-ship-gatesSkill
- knowledge-base-enrichmentSkill
- lean-context-layoutSkill
- local-inference-tuningSkill
- loop-hardening-contractSkill
- loopops-protocolSkill
- loop-readiness-reviewSkill
- lottie-motion-builderSkill
- minimal-diff-builderSkill
- motion-review-gateSkill
- overengineering-reviewSkill
- personal-workspace-routerSkill
- phase-spec-executionSkill
- pipeline-readiness-gateSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
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
- Distinctive: line 19
Default to three independent-review rounds, three fix cycles and a 30-minute CI observation budget.
- Very specific: line 25
Use codex-review-loop if installed and native independent OpenAI review is available.
- Very specific: line 26
Use pr-write if installed, or follow repository PR conventions directly.
- Very specific: line 27
Use pr-ci-watch if installed or a bounded native watcher to assess the current head's CI, material findings, required approvals and …
- Distinctive: line 33
Never merge, enable auto-merge, enter a merge queue, push to the default branch or delegate those actions.
- Distinctive: line 35
Check existing auto-merge/queue state before updates.
- Very specific: line 37
Do not deploy, publish a package/release, delete data, close another PR or expand security permissions as part of preparing a PR.
“Common” is measured: kept by at least 6 in 10 of the 11 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
PR Ready
Carry the authorized goal through implementation, proof, independent review when available, PR creation and bounded CI observation. Stop before merging. Treat the user's task as authority; this skill never overrides host permissions, repository rules, privacy or production boundaries.
Establish scope and budget
Record the goal, acceptance criteria, non-goals, owned paths, current Git state and real target base. Use a task-owned branch; preserve unrelated user work and isolate when necessary.
Default to three independent-review rounds, three fix cycles and a 30-minute CI observation budget. A material goal change needs a new scope, not an unbounded continuation.
Work to the gate
- Implement the smallest correct change. Reproduce the original failure where practical.
- Prove the result with focused repository checks and actual runtime/UI evidence when required. Record pre-existing failures and unavailable evidence.
- Use
codex-review-loopif installed and native independent OpenAI review is available. Otherwise report the independent-review gap; never silently call another provider or claim self-review as independent approval. - Use
pr-writeif installed, or follow repository PR conventions directly. Commit and push only this task's reviewed work. Create or update the identified PR and verify its URL/head/base. - Use
pr-ci-watchif installed or a bounded native watcher to assess the current head's CI, material findings, required approvals and mergeability. Fix in-scope findings within the budget and re-verify after each behavior change or meaningful conflict resolution.
The subskills are composable helpers, not hidden installation dependencies. If missing, perform their essential steps directly and name capability gaps.
Enforce no merge
Never merge, enable auto-merge, enter a merge queue, push to the default branch or delegate those actions.
Check existing auto-merge/queue state before updates. If already enabled, disable or remove it only when the user authorized changing that state. Otherwise stop branch updates and report the exact blocker; do not race an automatic merge or silently change someone else's queue.
Do not deploy, publish a package/release, delete data, close another PR or expand security permissions as part of preparing a PR. Do not bypass protections or use --admin.
Verify and hand off
Refresh the exact head and base immediately before reporting. Check open/draft state, required checks on the current head, human review decisions, material unresolved findings, branch currency/conflicts and auto-merge/queue state.
Use these outcomes:
READY_FOR_REVIEW: implementation and checks are verified; required human review remains.READY_FOR_MERGE: every repository gate is satisfied, the final diff has required review evidence and the PR remains open and unmerged.BLOCKED: verification, independent-review requirement, capability or access is missing.BUDGET_EXHAUSTED: work remains when the budget ends.MERGED_EXTERNALLY: someone or an existing automation already merged it.
Unknown state is not readiness. End active watchers before handing off. Do not claim they will wake this conversation later.
Report the PR URL, head/base SHAs, outcome, proof, independent-review result or gap, unresolved findings and whether the PR is open/unmerged. A local build or a published branch alone is not a ready PR.
Provenance
Adapt t3dotgg/tstack full-stop and selected proof/gate ideas from full-send. Remove automatic merging, phrase-based permission overrides and T3-only tools.
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.

