harness-auditor

Audit codebases and generate a .harness/CODEBASE_UDIT.md planner-ready assessment with Context7 dependency verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/woink/harness-skills-plugin --skill harness-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-auditor
Source: https://github.com/woink/harness-skills-plugin/tree/main/skills/harness-auditor
Command: npx skills add https://github.com/woink/harness-skills-plugin --skill harness-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The harness-auditor turns an existing repository into a precise, planner-ready assessment so the planner can produce realistic enhancement or remediation specs instead of imagining features from scratch. It prevents wasted effort by revealing architecture, dependency risks, test gaps, and UI baselines that must guide any incremental work.

Core Features & Use Cases

  • Directory reconnaissance: map project layout, detect root markers and source/test locations.
  • Dependency & stack inventory: parse manifests and verify versions and deprecations using Context7.
  • Architecture & code quality analysis: document patterns, data flow, type safety, error handling, and complexity hotspots.
  • Test coverage & CI checks: run or estimate test coverage and surface missing test regions.
  • UI baseline (web apps): optionally start the app and capture Playwright-driven screenshots and interaction checks.
  • Git history analysis & technical debt: summarize commit health, contributor activity, and prioritize debt into an actionable backlog for the planner.
  • Output: writes .harness/CODEBASE_AUDIT.md for the planner to consume.

Quick Start

Run the harness-auditor on the current repository to generate .harness/CODEBASE_AUDIT.md and a prioritized technical debt inventory.

Frequently Asked Questions about harness-auditor

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

FAQPage Schema
How do I audit an existing codebase to inventory dependencies and architecture?

Auditing an existing codebase involves mapping the project layout, parsing manifests to inventory dependencies, and analyzing architecture patterns to produce a structured assessment. The harness-auditor automates this to generate a planner-ready codebase audit file.

Can I run Playwright UI checks during a codebase audit?

Yes, you can optionally run Playwright-driven UI checks during a codebase audit if a live web app is available. The harness-auditor starts the app to capture screenshots and interaction checks alongside test execution and dependency verification.

What's the best way to verify dependency status and deprecations using Context7?

Verifying dependency status with Context7 involves parsing project manifests and querying the service to detect deprecated or outdated versions. The harness-auditor integrates this dependency verification directly into its stack inventory process.

How do I analyze git history and prioritize technical debt into an actionable backlog?

Analyzing git history to prioritize technical debt involves summarizing commit health, contributor activity, and complexity hotspots. The harness-auditor captures these git baselines to produce a prioritized, actionable debt backlog for the planner.

Do I need a live app running to generate a codebase audit?

No, a live app is not required to generate a codebase audit. The harness-auditor runs directory reconnaissance, dependency inventory, and static architecture analysis by default, only optionally starting the app for Playwright UI checks.

What output format does a codebase audit produce for the planner?

A codebase audit produces a structured markdown file at .harness/CODEBASE_AUDIT.md. This planner-ready output captures architecture analysis, test coverage gaps, and the prioritized technical debt inventory to guide incremental work.