Best use case
docs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate or update project documentation based on recent changes
Teams using docs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/docs/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/.claude/skills/docs/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/docs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How docs Compares
| Feature / Agent | docs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate or update project documentation based on recent changes
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Analyze recent code changes and update project documentation accordingly. If $ARGUMENTS is provided, focus documentation on that specific topic or file. Steps: 1. Run `git diff HEAD~5 --name-only` to find recently changed files 2. Read the changed files to understand what was modified 3. Check existing docs for sections that need updating 4. Update or create documentation to reflect the changes 5. Ensure code examples are accurate and up-to-date
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.