code-health

Run nightly code health reviews on git-scoped diffs from completion entries.

5|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill code-health-dbc-oduffy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-health
Source: https://github.com/dbc-oduffy/coordinator-claude/tree/main/plugins/coordinator/skills/code-health
Command: npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill code-health-dbc-oduffy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents silent regressions by reviewing the specific code surfaces touched on a given day and producing actionable health updates before the next session.

Core Features & Use Cases

  • Completion-entry scoped surface discovery: Determines what to review from today’s recorded completion entries, reducing wasted re-review of unchanged code.
  • Automated diff scoping and reviewer routing: Builds a targeted git diff scope and dispatches the appropriate domain reviewer with problems-only output.
  • Findings application with smart deferral: Applies straightforward fixes inline via a review integrator and defers complex, multi-file/new-abstraction issues into a structured debt backlog.
  • Health tracking artifacts: Updates a system health ledger and writes a morning-ready health summary, including grades and severity counts.

Quick Start

Use the skill by starting a workday completion flow that triggers /code-health, or run /code-health when prompted to review recent commits.

Frequently Asked Questions about code-health

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

FAQPage Schema
How do I automate a nightly code review for recent git diff changes?

Automated nightly code review scoping uses recorded completion entries to target only the surfaces touched that day, dispatching domain-specific problem-only reviewers to prevent silent regressions.

What is a health ledger and how does it track technical debt?

A health ledger tracks technical debt by recording deferred multi-file issues into a structured backlog, updating system health grades and severity counts for morning-ready review.

Can I run a code health review if my completion queries or tool binaries are missing?

Missing completion queries or tool binaries trigger failure-mode fallbacks, allowing the code health review to degrade gracefully rather than failing the entire nightly workflow.

How do I apply inline fixes from a code review and defer complex issues?

A review integrator applies straightforward fixes inline while deferring complex, multi-file or new-abstraction issues into a structured technical debt backlog for later resolution.

What's the best way to prevent code regressions in an end-of-day developer workflow?

End-of-day regression prevention runs a night-shift code health review over completion-entry scoped diffs, producing actionable health summaries with grades and severity counts before the next session.

Does code-health require a specific git-scoped diff generation setup?

Code-health requires git-scoped diff generation to build targeted review scopes, routing diffs to domain-specific reviewers and integrating findings into a health ledger.