coherence-auditor

Audits repository markdown files for broken links, unresolved TODOs, and git status issues.

1.0k|75|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/GoogleChrome/modern-web-guidance-src --skill coherence-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coherence-auditor
Source: https://github.com/GoogleChrome/modern-web-guidance-src/tree/main/.agents/skills/coherence-auditor
Command: npx skills add https://github.com/GoogleChrome/modern-web-guidance-src --skill coherence-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation in a growing repository drifts out of sync: relative links break, feature maps fall behind actual guides, TODO markers accumulate, and untracked files clutter the root. This Skill runs a structured audit that catches these issues before they reach a milestone commit.

Core Features & Use Cases

  • Link Integrity Check: Scans all markdown files and verifies that every relative link points to an existing file, reporting the file and line of any breakage.
  • Repository Health Checks: Verifies git working-tree state, warns when working directly on main, detects root clutter, and scans for unresolved TODO, TBD, and FIXME markers.
  • Sync and Coherence Validation: Confirms the feature map matches actual guides, checks skill configuration coverage, and runs a semantic consistency review across CONTEXT.md and project skills.
  • Use Case: Before merging a documentation update, invoke the audit to confirm no links broke, the feature map is current, and the working tree is clean.

Quick Start

Run the coherence audit across the repository documentation and report any broken links, out-of-sync files, or unresolved TODOs.

Frequently Asked Questions about coherence-auditor

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

FAQPage Schema
How do I check for broken links in markdown files?

Run the coherence audit script, which scans all markdown files excluding dist and node_modules and verifies every relative link resolves to an existing file. Broken links are reported with the file and line number plus a suggested fix.

How to audit documentation before a milestone commit?

Invoke the audit to run git status checks, link integrity scans, TODO detection, and feature map sync verification in one pass. A preflight flag additionally runs build, typecheck, lint, and the full test suite.

Does the audit modify repository files?

No, the audit is strictly read-only. The subagent runs checks and reports findings, warnings, and errors, but never edits files; fixes are applied separately after reviewing the report.

What does the feature map sync check verify?

It compares the features-and-use-cases guide against the actual guides present in the repository and reports when the mapping is out of sync, so documentation indexes stay accurate as guides are added or removed.

Why does the audit warn about working on the main branch?

The git state check flags a dirty working tree and warns when changes are made directly on main, since direct commits to main bypass review and increase the risk of inconsistent documentation reaching release.