deps-hygiene
Skill0 starsChanged 11 days agoMITView on GitHub
Clean up dependency drift, unused packages, and risky version ranges.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- api-and-interface-designSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- context-engineeringSkill
- debugging-and-error-recoverySkill
- deprecation-and-migrationSkill
- documentation-and-adrsSkill
- doubt-driven-developmentSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- idea-refineSkill
- incremental-implementationSkill
- interview-meSkill
- observability-and-instrumentationSkill
- performance-optimizationSkill
- planning-and-task-breakdownSkill
- security-and-hardeningSkill
- shipping-and-launchSkill
- source-driven-developmentSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- using-agent-skillsSkill
- kit-ci-triageSkill
- kit-evalsSkill
- kit-provider-adaptersSkill
- kit-releaseSkill
- kit-tuiSkill
- a11y-passSkill
- add-readmeSkill
- api-docsSkill
- changelogSkill
- cli-helpSkill
- code-reviewSkill
- completeness-qaSkill
- data-checkSkill
- fix-bugSkill
- project-setupSkill
- pr-readySkill
- ship-checklistSkill
- workspace-setupSkill
- write-testsSkill
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 15
Check for known vulnerabilities and abandoned packages when tooling is available.
- Distinctive: line 16
Prefer minimal version bumps that preserve lockfile integrity.
- Distinctive: line 17
Avoid drive-by major upgrades unless requested.
- Distinctive: line 18
After changes: install, build/test, and confirm lockfile updates are intentional.
≈ “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
Instructions
- Inventory direct dependencies and what they are for.
- Flag unused, duplicate, or overlapping packages.
- Check for known vulnerabilities and abandoned packages when tooling is available.
- Prefer minimal version bumps that preserve lockfile integrity.
- Avoid drive-by major upgrades unless requested.
- After changes: install, build/test, and confirm lockfile updates are intentional.
- Report:
- Removed / replaced
- Upgraded (and why)
- Left alone (and why)
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.