1natsu-document-harness-audit

Scan monorepo harness documentation and report seven categories of documentation issues.

1|Updated Oct 30, 2017
One-click install
npx skills add https://github.com/1natsu172/dotfiles --skill 1natsu-document-harness-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1natsu-document-harness-audit
Source: https://github.com/1natsu172/dotfiles/tree/main/.agents/skills/1natsu-document-harness-audit
Command: npx skills add https://github.com/1natsu172/dotfiles --skill 1natsu-document-harness-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill scans a project's harness documentation comprehensively (CLAUDE.md, .claude/rules/, docs/, feature READMEs) to detect duplicates, inconsistencies, obsolescence, broken references, gaps, inappropriate granularity, and missing references, and it proposes actionable improvements.

Core Features & Use Cases

  • Comprehensive harness documentation scanning across a monorepo to surface quality issues
  • Non-destructive workflow: scan, detect, propose, confirm, execute, and report without automatically applying changes
  • Clear integration with 1natsu-document-harness-model for placement decisions and reference flows

Quick Start

Run a scan to collect harness documents and generate a proposal list for review.

Frequently Asked Questions about 1natsu-document-harness-audit

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

FAQPage Schema
How do I audit harness documentation for consistency across a monorepo?

The audit evaluates seven categories of documentation problems: duplicates, inconsistencies, obsolescence, broken references, gaps, granularity deviations, and missing references, providing a prioritized list of proposals for review.

What is the best way to detect broken references and gaps in CLAUDE.md and .claude/rules/ files?

Scanning harness documentation detects broken references, identifies gaps, and surfaces granularity deviations across root and package docs, ensuring comprehensive coverage without making destructive changes.

Can I scan feature READMEs and docs in a monorepo without applying destructive changes?

The scan adheres to the 1natsu-document-harness-model for placement decisions to avoid destructive changes, ensuring all detected gaps and inconsistencies are reviewed before execution.

Does the documentation audit workflow support monorepo structures with multiple package docs?

It operates across monorepos by collecting harness documents from root and package directories, evaluating seven categories of problems, and generating a proposal list for human review.

Why does my harness documentation have duplicates and granularity deviations across packages?

Running a documentation audit evaluates seven categories of problems including duplicates and granularity deviations, using the 1natsu-document-harness-model for placement decisions to propose actionable improvements.

When do I need to run a full documentation audit across my project's harness files?

The audit detects obsolescence and missing references, providing a prioritized list of proposals for human review to ensure documentation quality and consistency without destructive changes.