pr-review-and-release
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
Use when preparing a pull request, judging release readiness, reviewing implementation risk with release discipline, writing release notes, checking CI, packaging artifacts, or deciding whether a repository is ready to ship.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-loop-designSkill
- ai-supply-chain-securitySkill
- anti-slop-pr-and-writingSkill
- authoring-portable-skillsSkill
- brainstormingSkill
- cross-language-portSkill
- giving-code-reviewSkill
- handoffSkill
- incident-responseSkill
- receiving-code-reviewSkill
- refactoring-safelySkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-agtmlsSkill
- verification-before-completionSkill
- vetting-a-skill-before-installSkill
- web-research-and-source-triageSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Use this skill for release readiness and review discipline.
- Distinctive: line 26
Run the full local gate before claiming readiness.
- Distinctive: line 27
Check release metadata, changelog, provenance, checksums, and docs freshness.
- Distinctive: line 29
Keep findings specific, file-backed, and ordered by severity.
- Distinctive: line 30
Do not publish if tests, docs, provenance, or security checks are stale.
≈ “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.
Files
PR Review And Release
Use this skill for release readiness and review discipline.
Workflow
- Inspect the diff and identify behavior, documentation, generated artifacts, and tests.
- Run the full local gate before claiming readiness.
- Check release metadata, changelog, provenance, checksums, and docs freshness.
- Summarize user-facing changes and operational risks.
- Keep findings specific, file-backed, and ordered by severity.
- Do not publish if tests, docs, provenance, or security checks are stale.
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.