docs

Automate documentation creation, updates, verification, and sync from codebase state.

11|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/dnviti/arsenale --skill docs-dnviti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/dnviti/arsenale/tree/main/.claude/skills/docs
Command: npx skills add https://github.com/dnviti/arsenale --skill docs-dnviti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation drift in a fast-moving codebase slows teams and causes misalignment between code and its docs. This Skill provides a structured, code-driven approach to manage all project documentation with clear workflows for creation, updates, verification, synchronization, and CLAUDE.md updates.

Core Features & Use Cases

  • Create, update, verify, sync, and claude-md operations driven by the repository state
  • Centralized guidance to keep docs in sync with code under the docs/ folder and related artifacts
  • Supports automation of standard documentation tasks from the codebase, reducing manual drift
  • Use Case: A developer changes an API or architecture file; run /docs update to regenerate relevant docs and ensure consistency

Quick Start

Use the docs skill to manage documentation tasks for the Arsenale project.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I prevent documentation drift when updating a fast-moving codebase?

Preventing documentation drift requires automating updates directly from codebase state. This approach orchestrates create, update, verify, and sync workflows to ensure docs reflect actual code changes, enforcing consistency across API, architecture, and governance contexts.

What is the best way to automate documentation updates after changing an API file?

The best way to automate documentation updates is by running a code-aware update workflow that regenerates relevant docs. This synchronizes the docs/ folder and related project artifacts precisely with the modified codebase state.

How does frontmatter-driven discovery work for project documentation?

Frontmatter-driven discovery works by enforcing structured metadata in documentation files to locate and manage them. It enables automated workflows to accurately identify, verify, and synchronize docs within the project structure.

Can I synchronize my CLAUDE.md file automatically with codebase changes?

Yes, you can synchronize your CLAUDE.md file automatically by using a dedicated claude-md workflow. It updates the file based on repository state to maintain alignment with current architecture and governance rules.

Does this documentation management approach work without external dependencies?

Yes, this documentation management approach works without external dependencies. It applies centralized guidance directly to the docs/ folder, CLAUDE.md, and related artifacts using internal codebase state.

When should I use a verification workflow for codebase documentation?

You should use a verification workflow for codebase documentation whenever you need to enforce consistency and check for drift. It validates structured sections and ensures docs accurately reflect actual code changes.