health

Detects leftover repository state and skill-catalog drift via a deterministic 16-area check engine.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/ozzy-labs/skills --skill health-ozzy-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/ozzy-labs/skills/tree/main/.claude/skills/health
Command: npx skills add https://github.com/ozzy-labs/skills --skill health-ozzy-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? After intensive repository work, developers often leave behind stale branches, orphaned worktrees, old stashes, interrupted merges, untriaged PRs, and draft releases. This Skill audits all of that in one shot and presents a fixed-vocabulary status table with recommended actions, so nothing is silently forgotten. ## Core Features & Use Cases - 16-area health audit: Runs the health-check.mjs engine to check interrupted git operations, conflict markers, working tree, stash, local branches, remote tracking, worktrees, submodules, tags, open PRs, assigned issues, review requests, failed CI runs, draft releases, automation PRs, and perspective frontmatter consistency. - Deep investigation mode: With --deep, performs read-only follow-up on items marked 要確認, upgrading labels where machine-decidable (e.g., stash apply-check, branch cherry detection against trunk). - Safe auto-fix with policy gates: With --fix, executes only reversible-local actions (prune / delete / fetch) immediately, while irreversible actions like stash drop require individual confirmation unless --yes explicitly overrides the central policy. - Use Case: At the end of a work session, run the health check to discover a forgotten stash, two merged branches, and an orphaned agent worktree, then clean them up safely with --fix. ## Quick Start Ask the assistant to run the health skill to check the repository for leftover state and show the status table.

Frequently Asked Questions about health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my git repository for leftover state after a work session?▼

Run the health skill, which executes the health-check.mjs engine to audit 16 areas including working tree, stash, branches, worktrees, and tags. It outputs a status table with fixed-vocabulary recommendations like prune, delete, push, or fetch.

How do I safely clean up merged branches and orphaned worktrees?▼

Run the health check with the --fix flag. It automatically executes reversible-local actions such as branch delete, worktree prune, and remote prune, while irreversible actions like stash drop require individual confirmation unless you pass --yes.

Does the health check work without the GitHub CLI installed?▼

Yes, git-based checks always run. Sections that depend on gh, such as open PRs, assigned issues, and failed CI runs, fail open with a per-section error note when gh is missing or unauthenticated.

What does the --deep flag do in a repository health check?▼

The --deep flag performs additional read-only investigation of items marked as needing confirmation. It can upgrade labels when machine-decidable, for example testing whether a stash applies cleanly to HEAD or whether branch commits are already merged into trunk.

Can the health check delete my stashes automatically?▼

No. Stash drop is classified as irreversible and gated as ask by the central policy, so it requires individual confirmation. Only an explicit --yes flag overrides the policy to execute it unattended.