skills.rest
axiomantic
axiomanticOFFICIAL
Explore all skills by this author →
GitHub

documentation-updates

Sync CHANGELOG, README, and docs after library changes.

8|5|Updated Dec 30, 2025
Search Tags:#automation#changelog#documentation#validation#readme#docs
One-click install
npx skills add https://github.com/axiomantic/spellbook --skill documentation-updates-axiomantic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: documentation-updates
Source: https://github.com/axiomantic/spellbook/tree/main/.claude/skills/documentation-updates
Command: npx skills add https://github.com/axiomantic/spellbook --skill documentation-updates-axiomantic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use after modifying library skills, library commands, or agents to ensure CHANGELOG, README, and docs are updated.

Core Features & Use Cases

  • Automatically generate and apply documentation updates after library changes.
  • Validate and refresh CHANGELOG totals, README links, and presence of reference docs.
  • Use Case: After adding or removing a library skill, run this to ensure docs reflect the current state.

Quick Start

Run the documentation-update workflow to synchronize all docs after a library change.

Frequently Asked Questions about documentation-updates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically update documentation after library changes?▼

To automatically update documentation after library changes, run a synchronization workflow that regenerates README links, adds CHANGELOG entries, and validates reference docs to match the current state.

How do I keep my changelog and README in sync after adding or removing skills?▼

Keeping your changelog and README in sync requires a validation pipeline that detects library modifications and automatically applies corresponding updates to all related documentation files.

What is the best way to validate that reference docs are present after modifying library commands?▼

Validating reference docs after modifying library commands is best handled by an automated documentation pipeline that checks doc presence, refreshes totals, and updates link references.

When do I need to run a documentation update workflow?▼

You need to run a documentation update workflow whenever skills, commands, or agents are added, modified, or removed, ensuring all documentation reflects the current library state.

Does the documentation synchronization process update link references automatically?▼

Yes, the documentation synchronization process automatically updates link references, validates CHANGELOG totals, and ensures README links accurately point to the current library components.

What happens if I don't update my library docs after changing agents or commands?▼

Without documentation updates after changing agents or commands, README links become outdated, CHANGELOG totals are incorrect, and reference docs will not reflect the current library state.

Related Skills

Explore More Content & Communication Skills→
jmdueajmduea

docs-freshness

Detect documentation drift from Rust, Python, and protocol changes.

Community
Intermediate
j0KZj0KZ

documentation-generation

Generate READMEs, changelogs, and API docs from TypeScript sources.

Community
Advanced
zircotezircote
3

documentation-standards

Audit Markdown documentation structure, formatting, links, and accessibility against defined standards.

Community
Advanced
MJ-AgentLabMJ-AgentLab

doc

Generate README.md and CHANGELOG.md documentation from n8n workflow.json files.

Official
Advanced