pr-delivery
Skill2 starsChanged 10 days agoNo licenceView on GitHub
Carry a change from "code is ready" to "PR merged". Use when preparing a branch and commits for review, writing or rewriting a PR title and body (Why, Summary visuals, Scope, Evidence, Merge Danger door and blast radius), opening a PR or a stack of PRs, babysitting a PR to merge-ready (watch-pr status watcher, merge frontier), classifying and fixing a red CI run, triaging human or bot review threads (Bugbot, security bots, linters that comment), or landing a verified stack bottom-up. Trigger on "open a PR", "write the PR description", "babysit this", "get it green", "why is CI red", "address the review comments", "is it mergeable", "land the stack", "merge when ready". Not for production release, deploys, or release notes; use project-release for those.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- microsoft/sre-agenttheir own version, first seen May 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- microsoft/sre-agent★ 187same 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 repository28 other files it gives its agents.
- adversarial-reviewSkill
- ask-ericSkill
- bug-diagnosisSkill
- business-discoverySkill
- codebase-investigationSkill
- decision-mappingSkill
- delivery-planningSkill
- delivery-proofSkill
- engineering-principlesSkill
- feature-implementationSkill
- idea-assessmentSkill
- issue-triageSkill
- multi-agent-deliverySkill
- performance-investigationSkill
- process-improvementSkill
- project-environmentSkill
- project-maintenanceSkill
- project-principlesSkill
- project-releaseSkill
- refactoringSkill
- session-continuitySkill
- standards-spec-reviewSkill
- system-verificationSkill
- technical-designSkill
- technical-writingSkill
- test-driven-developmentSkill
- verification-harnessSkill
- workflow-prototypeSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.