Menu
Audit changed dependencies for security, compatibility, lockfile hygiene, and necessity. Trigger when package manifests or lockfiles change.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Turn a specification into a concrete architecture with stable contracts, file boundaries, ownership, and risk analysis. Use this when acting as the architecture writer for a task.
Run the project verification stack after code changes. Trigger on code changes and stop on the first failure, fix it, then rerun the full stack from the top.
Verify that newly created files follow the repo's existing directory layout, naming conventions, and export patterns. Trigger when a new file is created.
Break architecture into execution-ready sub-tasks with clear ownership, dependencies, and contract references. Use this when acting as the planner for a task.
Use Playwright for browser automation, UI validation, E2E tests, and interaction debugging. Useful for flows that need real page navigation, assertions, screenshots, or request interception.
Final merge-readiness check after gates pass. Confirms verification is green, changed files are clean, and obvious release blockers are gone before merge.
| name | dependency-review |
| description | Audit changed dependencies for security, compatibility, lockfile hygiene, and necessity. Trigger when package manifests or lockfiles change. |
| owner | any |
| trigger | dependency_added |
| version | 2 |
Use this when package manifests or lockfiles change.
This skill applies to dependency changes:
package.json, lockfiles, workspace package manifestsCargo.toml, Cargo.lockpyproject.toml, requirements.txtgo.mod, go.sumIf the change is not dependency-related, return SKIPPED: Not a dependency change.
npm audit --production
cargo audit
pip-audit
If the audit tool is unavailable, say so explicitly instead of pretending the audit ran.
CLEAN: no dependency issues foundKeep this skill focused on dependencies. Do not turn it into a general implementation or architecture review.