health-audit

Audit repository drift, code quality, and test health in git-flow-next.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill health-audit-gittower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health-audit
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/health-audit
Command: npx skills add https://github.com/gittower/git-flow-next --skill health-audit-gittower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a structured health audit of the git-flow-next repository so you can catch documentation drift, stale skill references, duplicated logic, dead code, guideline violations, and real correctness bugs before they cause confusion or regressions.

Core Features & Use Cases

  • Documentation Drift Checks: Compares command flags, config keys, and root technical docs against the live codebase to find stale or missing references.
  • Skill and Guideline Consistency: Audits .claude/skills/ plus related guidance docs for broken links, overlap, or contradictions.
  • Code Quality and Correctness Review: Surfaces true duplication, dead code, unhandled errors, exit-code issues, and state or git-operation bugs with file-and-line evidence.
  • Test and Build Validation: Verifies build and test status, checks command coverage, and flags flaky or convention-breaking tests.
  • Use Case: Ask it to audit the repo after a burst of AI-assisted changes so you get a concise severity-ranked report and concrete next steps.

Quick Start

Run a full health audit of the repository and write the findings report for today’s date.

Frequently Asked Questions about health-audit

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

FAQPage Schema
How do I audit repository drift and catch documentation mismatches after code changes?

Repository drift audits compare command flags, config keys, and technical docs against the live codebase to find stale or missing references. This catches documentation mismatches before they cause regressions.

What is documentation drift and how do stale references impact code quality?

Documentation drift occurs when technical docs, command flags, or config keys fall out of sync with the live codebase. Stale references create confusion and regressions, requiring a structured audit to detect missing or outdated guidelines.

How do I check for dead code and duplicated logic with file-and-line evidence?

Checking for dead code and duplicated logic requires a code quality review that surfaces true duplication and unhandled errors with concrete file-and-line evidence. This produces severity-ranked audit reports for precise remediation.

Can I audit internal skill consistency and broken links in guidance docs?

Yes, you can audit internal skill consistency by checking `.claude/skills/` directories and related guidance docs. This identifies broken links, overlapping instructions, and contradictions across the repository's documentation.

What is the best way to validate test coverage and flag flaky tests in a repository?

The best way to validate test coverage is through test and build validation that verifies build status, checks command coverage, and flags flaky or convention-breaking tests. This ensures repository test health and stability.

Does a repository health audit require concrete file-and-line evidence for findings?

Yes, a repository health audit requires concrete file-and-line evidence for all findings. This ensures that severity-ranked audit reports provide actionable, verifiable corrections for code quality and correctness issues.