skills

Land approved pull requests — merge each approved, bot-owned PR that is ready to merge, strip its issue's in-progress label, then tear down the local worktree and branch. Human-invoked only. Use when the maintainer has approved a PR and wants it merged and cleaned up, says "land it" / "land the approved PRs" / "merge and clean up", or just approved a PR review.

Sweep workflow state for staleness and clean it up, one human-confirmed action at a time — abandoned claims, quiet needs-info issues, orphaned worktrees and branches, and epics whose children have all closed. Human-invoked only. Use when the maintainer wants to tidy up stale workflow state, reap abandoned claims, clear orphaned worktrees, says "reap" / "clean up the workflow" / "sweep for staleness", or notices a crashed run left an issue stuck in-progress.

Audit a codebase for high-risk untested paths and surface them as findings. Static-first, no instrumented coverage run required. Use when the user wants to find test gaps, audit coverage, find untested critical paths, or asks "what's not tested?".

Sweep a codebase for dead code — unreachable branches, never-called functions, orphaned modules — and surface each as a finding. Static-first, no tool run required. Use when the user wants to find dead code, hunt unreachable or unused code, find orphaned modules, or asks "what's unused?" / "what can we delete?".

Harvest in-code debt markers (TODO/FIXME/HACK/XXX and known shortcuts) from a codebase and surface each as a finding, clustered by area. Static-first, no debt tool required. Use when the user wants to harvest TODOs, find tech debt, audit shortcuts, or asks "what's left to clean up?".

Sweep a codebase for unhealthy third-party dependencies — outdated majors on load-bearing deps, versions with known advisories, abandoned upstreams, and license drift — and surface each as a finding. Static-first, reads manifests and lockfiles, no installs or tool runs required. Use when the user wants to audit dependencies, find outdated or vulnerable deps, check for abandoned upstreams, or asks "what are we depending on that's risky?".

Audit a codebase for documentation that has drifted out of sync with the code — stale vocabulary, violated decisions, README/behavior claims the code no longer backs — and surface each as a finding. Static-first, no tool run required. Use when the user wants to check the docs are still accurate, find stale docs, or asks "is the documentation still accurate?" / "what drifted from the docs?".

4 hooks across 2 events