package-release
Skill78 starsChanged 3 months agoMITView on GitHub
Use this skill when preparing Laravel package releases: CHANGELOG.md updates, generated release notes, GitHub release workflows, version checks, tags, release validation, or release automation changes. Never publish autonomously.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- jean1880/nuvek-agent-configtheir own version, first seen Nov 1, 2026
- peteonrails/voxtypetheir own version, first seen Oct 8, 2026
- aditya-deokar/software-factorytheir own version, first seen Sep 29, 2026
- ropensci-review-tools/ropensci-skillstheir own version, first seen Jun 24, 2026
- dannote/dot-pitheir own version, first seen Jun 13, 2026
- jessepinkman9900/claude-second-braintheir own version, first seen Apr 20, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- peteonrails/voxtype★ 1.8ksame name
- dannote/dot-pi★ 57same name
- jessepinkman9900/claude-second-brain★ 46same name
- ropensci-review-tools/ropensci-skills★ 8same name
- aditya-deokar/software-factory★ 0same name
- jean1880/nuvek-agent-config★ 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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- md/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/llms-full.txtllms.txt
- docs/llms.txtllms.txt
- package-compatibilitySkill
- package-generate-skillSkill
- package-scaffoldSkill
- package-testingSkill
- package-compatibilitySkill
- package-generate-skillSkill
- package-releaseSkill
- package-scaffoldSkill
- package-testingSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
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
- Distinctive: line 21
Do not tag, push, or publish without explicit user approval.
- Very specific: line 34
Update release notes grouping in .github/release.yml when a new label convention is added.
“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
Package Release
Primary Goal
Prepare a safe package release checklist and implementation without tagging, pushing, or publishing unless the user explicitly approves that action.
Workflow
- Review
CHANGELOG.md, generated release notes config, GitHub release workflows, open diff, and pending package changes. - Validate the release state with
composer testbefore recommending a release. - Confirm whether version metadata needs to change; many Laravel packages rely on Git tags rather than a hardcoded package version.
- Review tag naming, release branch, and GitHub release workflow behavior before any release command.
- Do not tag, push, or publish without explicit user approval.
References
CHANGELOG.md.github/release.yml.github/workflows/update-changelog.yml.github/workflows/tests.ymlcomposer.json
Examples
- Prepare a release by checking changelog coverage, confirming generated release notes categories, running
composer test, and drafting the tag command for user approval. - Update release notes grouping in
.github/release.ymlwhen a new label convention is added.
Anti-Patterns
- Creating tags, pushing branches, or publishing releases without explicit approval.
- Skipping
composer testbefore a release recommendation. - Treating generated release notes as a replacement for meaningful
CHANGELOG.mdentries. - Changing release workflows without checking the supported matrix in
.github/workflows/tests.yml.
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.

