audit

Audit docs, code, configs, tests, and specs for cruft and health issues.

1|2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/kynetic-ai/kynetic-spec --skill audit-kynetic-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/kynetic-ai/kynetic-spec/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/kynetic-ai/kynetic-spec --skill audit-kynetic-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies cruft, gaps, and health risks across docs, code, config, tests, and specs to ensure a clean, release-ready codebase. It coordinates parallel exploration and interactive triage to drive concrete cleanup actions and accountability.

Core Features & Use Cases

  • Parallel discovery: concurrently review docs (*.md), source code, configs (package.json, tsconfig, etc.), tests, and specs to surface issues.
  • Structured findings: generate file-level issues with location, description, severity, and recommended action.
  • Actionable outputs: create tasks and inbox items to track remediation and decisions during release readiness.
  • Use Case: pre-release cleanup, onboarding to large refactors, and ongoing health checks to prevent regressions.

Quick Start

Perform a full repository audit to surface cruft, then kick off triage and task creation.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I identify cruft and health issues across my codebase before a release?

To identify cruft before a release, perform a parallel codebase audit that concurrently reviews docs, source code, configs, tests, and specs to surface file-level issues with severity and recommended cleanup actions.

What is a codebase health check and when do I need one?

A codebase health check is a parallel review of docs, code, configs, tests, and specs to find cruft and gaps. You need one for pre-release cleanups, onboarding to large refactors, or periodic maintenance to prevent regressions.

Can I audit package.json, tsconfig, and markdown docs in parallel for release readiness?

Yes, you can audit package.json, tsconfig, markdown docs, source code, and tests in parallel. This concurrent exploration surfaces structured findings with location, issue description, and recommended action for release readiness.

What's the best way to triage codebase cruft and track remediation tasks?

The best way to triage cruft is to generate structured findings with location and severity, then automatically create tasks and inbox records to track remediation decisions and maintain accountability during release readiness.

Does a pre-release codebase audit work for onboarding to large refactors?

Yes, a pre-release codebase audit works for refactor onboarding by using parallel exploration to surface cruft, gaps, and health risks across all repository files, generating actionable tasks to guide the refactor process.

What limitations exist when running a parallel repository audit on large codebases?

The parallel repository audit requires a parallel exploration workflow to coordinate concurrent file reviews across docs, code, configs, tests, and specs, generating structured findings and task records for traceability.