code-documentation-analyzer — Claude Code skill for code docs analysis
Auto-activating skill for auditing code documentation: API references, user guides, architecture docs. Triggers on phrases like "code documentation analyzer" or "code analyzer".
MIT 1 installs ★ 2,935 updated 2026-11-01
npx skills add jeremylongshore/tons-of-skills-marketplace --skill code-documentation-analyzer -a claude-codeWhat code-documentation-analyzer does
This skill handles technical documentation work: API references, user guides, architecture descriptions, and documentation automation. It turns on by itself when a request contains "code documentation analyzer", "code analyzer", or "analyze code documentation r".
The skill walks through documentation tasks step by step, produces configs and code, then checks the output against common standards. Tool access is limited to Read, Write, Edit, Bash(cmd:*) and Grep. The Bash restriction matters: only named commands run, not arbitrary scripts.
You need a working dev environment and basic familiarity with technical docs before it will be useful. The skill sits in the Technical Documentation category with tags documentation, markdown, api-docs, readme, technical-writing. It ships inside the jeremylongshore/tons-of-skills-marketplace repo, where many skills share one generic README.
What it helps with
- audit API docs against the actual code
- generate a config for a documentation tool
- validate docs against common standards
- get a step-by-step plan for a docs task
- pull examples and patterns for technical writing
Example prompts for the agent
- Help me with code documentation analyzer for our API reference
- Analyze the code documentation in this repo and suggest improvements
- Generate a configuration for the documentation analyzer from my project
How to install code-documentation-analyzer
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill code-documentation-analyzer -a claude-code2Manually: put the files in place
~/.claude/skills/code-documentation-analyzer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/code-documentation-analyzer/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill code-documentation-analyzer -a codex2Manually: put the files in place
.agents/skills/code-documentation-analyzer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill code-documentation-analyzer -a cursor2Manually: put the files in place
.cursor/skills/code-documentation-analyzer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jeremylongshore/tons-of-skills-marketplace skills/17-technical-docs/code-documentation-analyzer2Manually: put the files in place
.github/skills/code-documentation-analyzer/SKILL.md1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill code-documentation-analyzer -a gemini-cli2Platform CLI
gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace --path skills/17-technical-docs/code-documentation-analyzerManually: put the files in place
.devin/skills/code-documentation-analyzer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill code-documentation-analyzer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about code-documentation-analyzer
How do I install code-documentation-analyzer in Claude Code?
Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill code-documentation-analyzer -a claude-code. The skill lands in ~/.claude/skills/code-documentation-analyzer/SKILL.md.
What does code-documentation-analyzer do?
It audits code documentation: API references, user guides, architecture docs. It gives step-by-step guidance, generates configs, and validates results against standards.
Which tools can the skill use?
Read, Write, Edit, Bash(cmd:*) and Grep. Bash is restricted to named commands, so arbitrary scripts will not run.
Source text
SKILL.md · MIT
--- name: code-documentation-analyzer description: 'Analyze code documentation analyzer operations. Auto-activating skill for Technical Documentation. Triggers on: code documentation analyzer, code documentation analyzer Part of the Technical Documentation skill category. Use when analyzing or auditing code documentation analyzer. Trigger with phrases like "code documentation analyzer", "code analyzer", "analyze code documentation r". ' allowed-tools: Read, Write, Edit, Bash(cmd:*), Grep version: 1.0.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - documentation - writing compatibility: Designed for Claude Code --- # Code Documentation Analyzer ## Overview This skill provides automated assistance for code documentation analyzer tasks within the Technical Documentation domain. ## When to Use This skill activates automatically when you: - Mention "code documentation analyzer" in your request - Ask about code documentation analyzer patterns or best practices - Need help with technical documentation skills covering api docs, user guides, architecture docs, and documentation automation. ## Instructions 1. Provides step-by-step guidance for code documentation analyzer 2. Follows industry best practices and patterns 3. Generates production-ready code and configurations 4. Validates outputs against common standards ## Examples **Example: Basic Usage** Request: "Help me with code documentation analyzer" Result: Provides step-by-step guidance and generates appropriate configurations ## Prerequisites - Relevant development environment configured - Access to necessary tools and services - Basic understanding of technical documentation concepts ## Output - Generated configurations and code - Best practice recommendations - Validation results ## Error Handling | Error | Cause | Solution | |-------|-------|----------| | Configuration invalid | Missing required fields | Check documentation for required parameters | | Tool not found | Dependency not installed | Install required tools per prerequisites | | Permission denied | Insufficient access | Verify credentials and permissions | ## Resources - Official documentation for related tools - Best practices guides - Community examples and tutorials ## Related Skills Part of the **Technical Documentation** skill category. Tags: documentation, markdown, api-docs, readme, technical-writing
© Jeremy Longshore · MIT · jeremylongshore/tons-of-skills-marketplace