REQUIRED READING: Always load references/documentation-guide.md to:
Validate existing documentation - Check if suggested docs follow correct structure, style, and alignment
Guide updates - Reference standards when writing or updating documentation
The guide contains all standards, examples, patterns, and requirements. Do not make assumptions about documentation format, style, or structure - always reference the guide.
Documentation Guide: references/documentation-guide.md - REQUIRED: Complete documentation standards, style, structure, and examples. Load this file to validate existing docs and guide updates.
docs-write skill: skills/docs-write/SKILL.md - Complete workflow for writing/updating documentation
Output
The tool outputs:
Changed code files organized by category
Suggested documentation files to review
Guidance on what needs to be updated
Best Practices
Run this check before committing significant changes
Always load references/documentation-guide.md to validate documentation structure and alignment
Verify existing documentation follows guide standards (style, structure, format) - not just detect what needs updating
Review the Documentation Guide to understand what changes require documentation
Update documentation in the same PR as code changes
Fix structure/alignment issues when updating content
Use the verbose mode for more detailed information
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: lukasstrickler-ai-dev-atelier-docs-check3description: Documentation Check4---56# Documentation Check78## Tools910- `ada::docs:check` - Analyzes git diff and suggests documentation updates1112## What It Detects1314The tool categorizes changes and suggests relevant documentation files:1516- **Database/Schema changes** → suggests `.docs/db/` files17- **API changes** → suggests `.docs/api/` and `.docs/workflow/` files18- **Component/UI changes** → suggests component documentation19- **Configuration changes** → suggests setup/install documentation20- **Authentication changes** → suggests auth documentation21- **Test changes** → suggests test documentation22- And more...2324## Workflow25261. **Run check**: `bash skills/docs-check/scripts/check-docs.sh` (or `--verbose` for details)27 - Analyzes git diff for code changes requiring documentation updates28292. **Review output**: Categorized changes with suggested documentation files30313. **Validate structure**: Read `references/documentation-guide.md` to verify existing docs follow standards32334. **Update documentation**: Use `skills/docs-write/SKILL.md` workflow, reference `references/documentation-guide.md` for requirements34355. **Verify**: Re-run check until all suggestions addressed3637### Integration with Other Skills3839- Run after `ada::code-review` to check if reviewed changes need documentation40- Run before `ada::code-quality` finalization to ensure docs are updated with code41- Use during PR preparation to ensure documentation is complete4243## Examples4445### Example 1: Basic Usage4647```bash48bash skills/docs-check/scripts/check-docs.sh49```5051### Example 2: Verbose Mode5253```bash54bash skills/docs-check/scripts/check-docs.sh --verbose55```5657## References5859**REQUIRED READING**: Always load `references/documentation-guide.md` to:601. **Validate existing documentation** - Check if suggested docs follow correct structure, style, and alignment612. **Guide updates** - Reference standards when writing or updating documentation6263The guide contains all standards, examples, patterns, and requirements. Do not make assumptions about documentation format, style, or structure - always reference the guide.6465- **Documentation Guide**: `references/documentation-guide.md` - **REQUIRED**: Complete documentation standards, style, structure, and examples. Load this file to validate existing docs and guide updates.66- **docs-write skill**: `skills/docs-write/SKILL.md` - Complete workflow for writing/updating documentation6768## Output6970The tool outputs:71- Changed code files organized by category72- Suggested documentation files to review73- Guidance on what needs to be updated7475## Best Practices7677- Run this check before committing significant changes78- **Always load `references/documentation-guide.md`** to validate documentation structure and alignment79- Verify existing documentation follows guide standards (style, structure, format) - not just detect what needs updating80- Review the [Documentation Guide](references/documentation-guide.md) to understand what changes require documentation81- Update documentation in the same PR as code changes82- Fix structure/alignment issues when updating content83- Use the verbose mode for more detailed information8485---86> Converted and distributed by [TomeVault](https://tomevault.io/claim/lukasstrickler) — claim your Tome and manage your conversions.87<!-- tomevault:4.0:skill_md:2026-04-13 -->
Run npx skillmds@latest add tomevault-io/lukasstrickler-ai-dev-atelier-docs-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Documentation Check It is listed under Docs & Writing on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.