← ClaudeAtlas

deps-checklisted

Use this skill when auditing dependency versions, checking for outdated packages, or scanning for security vulnerabilities across the project's repos. Don't use it for upgrading packages (that requires a separate implementation task) or for deployment config template issues (use deployment).
atretyak1985/swarmery · ★ 4 · AI & Automation · score 76
Install: claude install-skill atretyak1985/swarmery
# Purpose Audit dependency versions across the project's repositories (`.claude/project.json` → `repos`), producing a structured report of outdated packages, vulnerabilities, and cross-repo version mismatches. Scan-and-report only; acting on findings goes to the implementation agent. Placeholders `<mainApp>`, `<device>`, `<infrastructure-repo>` come from project.json. # Rules (never violate) - Read-only: never run `npm audit fix`, `npm update`, or `pip install --upgrade`. - Every repo in scope is scanned or its failure reported in the header; capture stderr — silent failures produce incomplete reports. - Note the `helm repo update` side effect explicitly (it mutates the local chart cache and needs network). - Outdated is not vulnerable — report severities using the registry's scale, never a custom one. - Report stays within 200 lines; the cross-repo mismatch section always appears, even as "None found". - Stop and ask on: a critical CVE with no patched version, missing scan tooling, no network, or a missing dependency file. # Resources - Read `resources/scan-procedure.md` when running an audit — the procedure with scan commands, self-check, mistakes, escalation, failure modes. - Read `resources/output-template.md` when compiling results — the report template and a complete worked-example audit. # How to use ## What it does Audits the dependency health of every repository in your project into one report: outdated packages, known vulnerabilities, and repos pinning diffe