dependency-release-guard
Skill2 starsChanged 3 months agoMITView on GitHub
Review dependency updates, package manager files, lockfiles, CI workflows, release scripts, generated artifacts, and publish steps for regressions and supply-chain risk. Use when maintainers are preparing releases, reviewing Dependabot/Renovate PRs, updating packages, or checking build and publish automation.
In this repository2 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 8
Use this skill before merging dependency changes or publishing releases.
- Distinctive: line 20
Check whether the change affects runtime, development, build, test, or publish behavior.
- Distinctive: line 25
Look for risk signals:
- Distinctive: line 55
Do not recommend publishing, deploying, or pushing tags unless the maintainer explicitly requested that action and the required checks …
≈ “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
Dependency Release Guard
Use this skill before merging dependency changes or publishing releases.
Review Workflow
- Identify changed dependency surfaces:
- manifest files
- lockfiles
- CI workflow files
- build scripts
- release scripts
- generated artifacts
- package registry metadata
- Check whether the change affects runtime, development, build, test, or publish behavior.
- Inspect scripts that can execute automatically:
preinstall,install,postinstallprepare,prepublishOnly,release- CI and deployment steps
- Look for risk signals:
- new transitive dependency with broad permissions
- lockfile churn unrelated to the stated update
- unpinned GitHub Actions or container images
- package name confusion or registry changes
- generated files changed without source changes
- release credentials used in overly broad contexts
- Recommend validation:
- install from a clean checkout
- run unit tests
- run build
- inspect package contents before publish
- dry-run release if supported
Output Format
Release Risk
- Low/Medium/High and why.
Findings
- file:line - concrete risk or regression.
Required Checks
- commands or review steps to run before merge/release.
Maintainer Recommendation
- merge, block, or request changes.Do not recommend publishing, deploying, or pushing tags unless the maintainer explicitly requested that action and the required checks passed.
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.