code-health

Scan codebases for quality issues and create tech-debt tasks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/N2O-com/N2O-just-workflow --skill code-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-health
Source: https://github.com/N2O-com/N2O-just-workflow/tree/main/02-agents/code-health
Command: npx skills add https://github.com/N2O-com/N2O-just-workflow --skill code-health

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically scans your codebase for common quality issues like excessive file length, missing documentation, dead code, and lack of test coverage, helping to proactively manage technical debt.

Core Features & Use Cases

  • Comprehensive Audits: Performs 6 parallel checks for file length, missing docs, function density, circular dependencies, dead exports, and test coverage gaps.
  • Configurable: Uses built-in defaults or a custom .pm/code-health.yml for thresholds and scope.
  • Task Creation: Automatically generates tech-debt tasks for critical and warning findings.
  • Integration: Can be invoked standalone, by tdd-agent for changed files, or by pm-agent as a baseline scan.
  • Use Case: Run a full code health audit before starting a new sprint to identify and prioritize areas needing refactoring or documentation.

Quick Start

Run a full code health audit across the repository.

Frequently Asked Questions about code-health

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

FAQPage Schema
How do I audit codebase quality and find tech debt automatically?

To audit codebase quality and find tech debt automatically, run a full repository scan to check file length, missing documentation, function density, circular dependencies, dead exports, and test coverage gaps.

What is the best way to track technical debt during a sprint?

The best way to track technical debt during a sprint is to run a code health audit that automatically generates tech-debt tasks for critical and warning findings, helping you prioritize refactoring needs.

Can I configure thresholds for file length and missing documentation checks?

Yes, you can configure thresholds for file length and missing documentation checks by creating a custom `.pm/code-health.yml` file, or you can rely on the built-in default thresholds for your scans.

How does code health scanning work for changed files?

Code health scanning for changed files works by integrating with `tdd-agent`, which invokes the audit on modified files rather than the full repository to identify issues like circular dependencies and test coverage gaps.

Why should I scan for dead exports and circular dependencies?

You should scan for dead exports and circular dependencies to proactively manage technical debt, reduce dead code, and prevent architectural issues that complicate future refactoring and module maintenance.

Does the code health audit integrate with project management workflows?

Yes, the code health audit integrates with project management workflows by working with `pm-agent` for baseline scans and `tdd-agent` for changed files, ensuring automated checks across your development workflow.