harness-repo-map

Restructures bloated CLAUDE.md files into a map plus structured docs/ knowledge base.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/zhengguangli/harness-engineering-kit --skill harness-repo-map-zhengguangli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-repo-map
Source: https://github.com/zhengguangli/harness-engineering-kit/tree/main/skills/harness-repo-map
Command: npx skills add https://github.com/zhengguangli/harness-engineering-kit --skill harness-repo-map-zhengguangli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Repository knowledge crammed into an oversized CLAUDE.md consumes agent context, cannot be mechanically validated, and rots quickly. This Skill converts that encyclopedia-style entry file into a progressive disclosure model: a slim CLAUDE.md map pointing to structured docs/ files that agents can discover and verify. ## Core Features & Use Cases - CLAUDE.md Slimming: Splits a bloated CLAUDE.md (over 100 lines) by topic into docs/ files and rewrites it as a pointer table with a navigation map. - Docs Skeleton Creation: Builds the docs/ structure from scratch (ARCHITECTURE.md, QUALITY_SCORE.md, design-docs/, exec-plans/, product-specs/) using provided templates. - Inline Document Auditing: The doc-gardener agent runs four read-only checks — broken-link detection, freshness checks (30-day staleness), coverage checks against code domains, and structure checks — with severity-rated repair instructions. - Use Case: A React project's CLAUDE.md has grown to 350 lines mixing architecture, API docs, and deployment notes. The Skill migrates content into docs/, rewrites CLAUDE.md as an 80-line map, and validates that all navigation links resolve. ## Quick Start Use the harness-repo-map skill to slim my oversized CLAUDE.md into a navigation map and reorganize the content into a structured docs/ directory.

Frequently Asked Questions about harness-repo-map

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

FAQPage Schema
How do I slim down a bloated CLAUDE.md file?▼

Split the CLAUDE.md content by topic into docs/ files such as ARCHITECTURE.md and design-docs/, then rewrite CLAUDE.md as a pointer table under 100 lines. Keep only a repository overview, a few hard constraints, and a navigation table.

How to detect broken links in a docs/ directory?▼

The doc-gardener agent enumerates files with find docs -type f, extracts markdown links, and verifies each target exists. After fixing links, run find docs -name '*.md' -exec grep -l '](' {} \; to confirm no residual broken links remain.

What is progressive disclosure for agent documentation?▼

Progressive disclosure means the agent starts from a small entry file (CLAUDE.md as a map) and is directed where to find deeper information in docs/. It avoids cramming all knowledge into one file, which wastes context and cannot be mechanically validated.

When should I not restructure my repository documentation?▼

Skip restructuring for very small projects like single-file scripts, when you only need to update one specific document, or when the project needs full harness initialization including .gitignore and CI — use harness-bootstrap for that instead.

How do I keep documentation from going stale?▼

Require a last-validated date on key documents and flag any over 30 days old as pending verification. Use git history as an implicit signal: a document unchanged for 60+ days while surrounding code evolved is likely stale.