release-review
Skill1.4k starsChanged 14 days agoMITView on GitHub
Review a StarPie release candidate for version consistency, package boundaries, plugin distribution rules, evidence completeness, upgrade behavior, and authorization before merge, tags, installers, or GitHub Release publication.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- arvindand/agent-skillstheir own version, first seen Nov 1, 2026
- pariveo/salesforce-agent-skillstheir own version, first seen Oct 20, 2026
- Shri-Phnx/claude-skillstheir own version, first seen Oct 13, 2026
- m4r1k/Enerutheir own version, first seen Oct 9, 2026
- nielsmadan/skillstheir own version, first seen Sep 5, 2026
- indyforge/knowledge-forgetheir own version, first seen Jun 18, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- m4r1k/Eneru★ 152same name
- arvindand/agent-skills★ 17same name
- pariveo/salesforce-agent-skills★ 2same name
- peterwangze/software-project-governance★ 2same name
- Shri-Phnx/claude-skills★ 2same name
- nielsmadan/skills★ 1same name
- indyforge/knowledge-forge★ 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bug-investigationSkill
- feature-planningSkill
- regression-testingSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 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
- Very specific: line 8
Read the root AGENTS.md, docs/release.md, docs/testing.md, and any domain document touched by the candidate.
- Distinctive: line 21
All version synchronization points agree.
- Distinctive: line 22
No unrelated dirty files or worktree artifacts enter the candidate.
“Common” is measured: kept by at least 6 in 10 of the 6 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
StarPie Release Review
Read the root AGENTS.md, docs/release.md, docs/testing.md, and any domain document touched by the candidate.
Review inputs
- exact candidate commit and target branch;
- diff and commit trail;
- version target and changelog entry;
- build/test receipts tied to the candidate;
- human acceptance status;
- intended artifacts and external operations.
Checks
- All version synchronization points agree.
- No unrelated dirty files or worktree artifacts enter the candidate.
- Main packages do not contain official plugin DLLs or the legacy plugin source directory.
- Clean data startup performs no silent network/install; installed plugins still work offline.
- Lightweight, Standalone and Setup outputs match naming and content rules.
- SHA-256 values are generated from final artifacts, not pre-final files.
- Upgrade/install paths preserve user configuration and do not silently enable plugins.
- Required independent review and human gates are complete.
Authorization boundary
Review and preparation do not authorize commit, push, merge, Tag, installer publication or GitHub Release. Identify the next external action and obtain explicit authorization for it. If the requested version is wrong or an artifact is already public, stop and propose recovery; never silently overwrite release history.
Return a verdict of approve, request changes, or blocked, with concrete evidence and unverified items.
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.

