Claude-skill-registry doc-automation
Documentation automation with file versioning and metadata. Use for maintaining documentation, tracking file versions, adding metadata headers.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/doc-automation" ~/.claude/skills/majiayu000-claude-skill-registry-doc-automation && rm -rf "$T"
manifest:
skills/data/doc-automation/SKILL.mdsource content
Documentation Automation Skill
Automate documentation maintenance with consistent versioning and metadata.
Core Functions
1. File Metadata Standard
Every tracked file should have metadata. Format depends on file type:
Markdown Files (.md)
--- version: "1.0.0" created: "YYYY-MM-DD" updated: "YYYY-MM-DD" author: "agent-name or user" status: "draft|active|deprecated" ---
JSON Files (.json)
{ "_meta": { "version": "1.0.0", "created": "YYYY-MM-DD", "updated": "YYYY-MM-DD", "schema": "schema-name" } }
TypeScript/JavaScript (in comments)
/** * @version 1.0.0 * @created YYYY-MM-DD * @updated YYYY-MM-DD * @author agent-name */
2. Versioning Rules
Follow semantic versioning:
- Major (X.0.0): Breaking changes, complete rewrites
- Minor (0.X.0): New features, significant additions
- Patch (0.0.X): Bug fixes, small updates, metadata changes
3. Automatic Metadata Updates
When editing files:
- Check if metadata exists
- If missing, add with version 1.0.0
- If exists, increment version appropriately
- Update
date to todayupdated - Keep
date unchangedcreated
4. Version Tracking File
Maintain
.ai/versions.json for project-wide version tracking:
{ "_meta": { "version": "1.0.0", "updated": "YYYY-MM-DD" }, "files": { "path/to/file.md": { "version": "1.2.0", "created": "YYYY-MM-DD", "updated": "YYYY-MM-DD", "changelog": [ { "version": "1.2.0", "date": "YYYY-MM-DD", "change": "Added section X" }, { "version": "1.1.0", "date": "YYYY-MM-DD", "change": "Expanded examples" }, { "version": "1.0.0", "date": "YYYY-MM-DD", "change": "Initial creation" } ] } } }
Tracked File Types
| Type | Track Versions | Metadata Location |
|---|---|---|
| Yes | YAML frontmatter |
| Yes | property |
| Optional | JSDoc header |
| Optional | Module docstring |
| Skills | Yes | YAML frontmatter |
| Agents | Yes | YAML frontmatter |
Commands
Add Metadata to File
When creating or significantly updating a file:
- Add appropriate metadata header
- Set version to 1.0.0 if new, increment if existing
- Update versions.json
Validate Documentation
Check all tracked files:
- Have proper metadata
- Versions match versions.json
- No stale files (updated > 90 days ago)
Generate Changelog
Extract changes from versions.json for release notes
Hook Integration
This skill works with the
progress-save hook to automatically:
- Track files modified in session
- Update versions.json on session end
- Ensure metadata consistency
Token Efficiency
- Metadata adds ~50 tokens per MD file
- versions.json is centralized, not loaded per-file
- Only load file versions when needed for comparison