dep-hygiene
Skill0 starsChanged 15 days agoNo licenceView on GitHub
Get a repository's dependencies clean, current and safe, both external packages and internal module boundaries. Inventories every manifest, lockfile and package manager, checks vulnerabilities and whether the vulnerable code is reachable, unused, missing and misplaced deps, overlapping libraries and duplicate versions, outdated and deprecated packages, version policy, and import cycles and layering violations. Verifies every finding and plans the work - reachable vulnerabilities first, removals, patch and minor updates per ecosystem, each major alone with its migration notes read. After approval, applies batches through the package manager, runs build, types, lint and tests after each, reverts a failing batch, and keeps a ledger. Use when the user asks to audit, clean up or upgrade dependencies, fix vulnerable packages, remove unused deps, or invokes /dep-hygiene (options --scope, --report-only, --audit-only, --no-major, --auto, --models). Never switches package manager or installs tools. Commits nothing.
- Installs packages
In this repository12 other files it gives its agents.
- conventionsSkill
- deep-reviewSkill
- deslopSkill
- error-pathsSkill
- guided-reviewSkill
- hotspotsSkill
- perf-passSkill
- pr-reviewSkill
- sdlc-fast-piSkill
- sdlc-fastSkill
- sdlc-loopSkill
- test-strengthSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 11 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.