docs-refresh

To keep skill documentation synchronized with source files automatically, you can use an automation script that parses `.claude/skills/*/skill.yaml` definitions to update `docs/skills/REFERENCE.md` and the skills table in `CLAUDE.md`.

To validate that project documentation is current in a CI/CD pipeline, implement validation checks that ensure generated documentation matches your skill definitions before commits and deployments, preventing outdated information.

Yes, you can use automation to update Claude instructions when skill definitions change by processing `.claude/skills/*/skill.yaml` files to automatically refresh the skills table within `CLAUDE.md`.

The best way to generate reference documentation for multiple skills is to run a deterministic generation workflow that extracts definitions from skill YAML files and compiles them into a centralized `REFERENCE.md` document.

Your documentation build fails after modifying skill definitions because validation checks detect a mismatch between the updated source files and the existing generated documentation, requiring you to refresh the docs to maintain integrity.

Yes, you need deterministic generation workflows to maintain documentation integrity, as they ensure consistent output for your reference docs and Claude instructions, which is required for reliable CI/CD validation checks.