docs-refresh

Regenerate CLAUDE.md and REFERENCE.md from .claude/skills/*/skill.yaml files.

2|1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/proven-xyz/proven-app --skill docs-refresh-proven-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-refresh
Source: https://github.com/proven-xyz/proven-app/tree/main/.agents/skills/docs-refresh
Command: npx skills add https://github.com/proven-xyz/proven-app --skill docs-refresh-proven-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically keeps documentation in sync with source files, reducing manual drift and maintenance overhead.

Core Features & Use Cases

  • Automates regeneration of docs/skills/REFERENCE.md and CLAUDE.md from .claude/skills/*/skill.yaml.
  • Tracks and applies changes to the project-wide documentation references used by Claude workflows.
  • Supports triggering via user commands (e.g., /docs-refresh) to refresh documentation on demand.

Quick Start

Ask your AI to run the docs refresh to regenerate the documentation from the latest source files.

Frequently Asked Questions about docs-refresh

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

FAQPage Schema
How do I keep CLAUDE.md and REFERENCE.md in sync with skill.yaml source files?

To keep CLAUDE.md and REFERENCE.md in sync with source files, you can automate documentation regeneration from .claude/skills/*/skill.yaml. This enforces deterministic generation to update project-wide references used by Claude workflows.

How do I automate documentation refresh from source files in Claude workflows?

You can automate documentation refresh from source files by triggering a command like /docs-refresh. This regenerates project documentation outputs on demand, ensuring generated references match the latest skill definitions without manual updates.

What is deterministic documentation generation and when do I need it for skill management?

Deterministic documentation generation automatically rebuilds reference files from structured source definitions like skill.yaml. You need it for skill management when maintaining multiple project-wide docs that must strictly reflect source file changes without manual drift.

Can I regenerate project-wide documentation references on demand without manual edits?

Yes, you can regenerate project-wide documentation references on demand. By triggering a refresh command, the system automatically updates docs/skills/REFERENCE.md and CLAUDE.md from skill.yaml files, eliminating the need for manual edits.

Why does my documentation drift from source files in automated workflows?

Documentation drifts from source files when updates are applied manually without a deterministic generation process. Automating the refresh from .claude/skills/*/skill.yaml ensures references stay synchronized and reduces ongoing maintenance overhead.

Are there limitations to automating docs refresh from skill.yaml files?

Automating docs refresh from skill.yaml files is limited to project-wide documentation workflows involving CLAUDE.md and REFERENCE.md. It does not manually track arbitrary file changes, relying instead on deterministic generation from defined skill structures.