Agent skill · Documentation

docs-analyzer

Analyzes code changes and identifies documentation gaps. Scans git history, catalogs existing docs, and generates comprehensive analysis reports.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill docs-analyzer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 8 KB
Bundled scripts: none
Allowed tools: ReadGrepGlobBash
Path: skills/analysis/docs-analyzer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Documentation Analyzer Skill ## Purpose This skill specializes in analyzing codebases to identify documentation gaps and assess the impact of code changes on existing documentation. It provides structured reports to guide documentation updates. ## When to Activate Use this skill when: - Starting documentation review for a project - Analyzing impact of recent code changes - Auditing documentation completeness - Preparing for documentation updates - User requests documentation analysis ## Core Workflow ### Step 1: Catalog Existing Documentation Scan and catalog all documentation files in the repository: **Documentation Files to Find**: - `README.md` (root and subdirectories) - `docs/` directory contents - `CONTRIBUTING.md` - `CHANGELOG.md` - `*.md` files throughout the codebase - API documentation (OpenAPI/Swagger specs) - Architecture diagrams and documentation **Use Glob and Read tools**: ```bash # Find all markdown files Glob: "**/*.md" # Find documentation directories Glob: "**/docs/**/*" # Find API specs Glob: "**/*.{yaml,yml,json}" (for OpenAPI specs) ``` **Catalog Output**: - List of all documentation files found - Brief description of each file's purpose - Last modified dat

What's inside
Steps it walks through
  1. Purpose
  2. When to Activate
  3. Core Workflow
  4. Step 1: Catalog Existing Documentation
  5. Step 2: Analyze Git History
  6. Step 3: Identify Affected Components
  7. Step 4: Detect Documentation Gaps
  8. Step 5: Assess Documentation Impact
  9. Step 6: Generate Analysis Report
  10. Output Specification
  11. Integration with Other Skills
  12. Example Usage
  13. Guidelines
  14. Do:
Ships with 1 file
  • metadata.json
Commands it runs
Find all markdown files
Find documentation directories
Find API specs
Get recent commits (last 10-50 depending on activity)
git log --oneline -20
Get detailed diff for recent changes
git diff HEAD~10..HEAD --stat
Identify changed files by type
git diff HEAD~10..HEAD --name-only
Get commit messages for context
More from claude-skill-registry
All skills →
About this skill
What does the docs-analyzer skill do?

Analyzes code changes and identifies documentation gaps. Scans git history, catalogs existing docs, and generates comprehensive analysis reports.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill docs-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going