health-checklisted
Install: claude install-skill tonmoy007/forge-plugins
# Forge Health Check
Runs the Health daemon (REQ-F-022..026). Executes hook unit tests as a subprocess,
checks `.forge/lessons.yaml` for structural integrity, and produces a markdown health
report. Overall status is `healthy`, `degraded`, or `failing` based on clear rules.
Auto-disable of hooks is gated on explicit policy and is **never silent**.
## When to Use
- User types `/forge:health-check` or asks to check if the plugin/hooks are working.
- After a session where hooks behaved unexpectedly.
- Before a release to verify the plugin is in good shape.
## When NOT to Use
- The user wants to run the full test suite — use `pytest tests/` directly.
- The user wants pipeline status (stage gates) — that is `/forge:status`.
## Steps
1. Run the health check:
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/health_check.py --run --cwd "$(pwd)"
```
2. Present the full markdown report verbatim. The report covers:
- **Hook tests**: pass/fail counts from hook-focused pytest run.
- **Lesson store**: any integrity issues in `.forge/lessons.yaml` (missing fields,
out-of-range confidence, broken `[[xref]]` cross-references, malformed YAML).
- **Status summary**: `HEALTHY`, `DEGRADED`, or `FAILING`.
3. Interpret the status for the user:
- **HEALTHY** — all hooks pass and lesson store is clean. No action needed.
- **DEGRADED** — hooks pass but lesson store has issues. Recommend reviewing
`.forge/lessons.yaml` and fixing flagged entries.
- **FAILING** —