update-docs

Map changed source files to documentation pages and apply updates.

29|6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/acartag7/edictum --skill update-docs-acartag7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/acartag7/edictum/tree/main/.claude/skills/update-docs
Command: npx skills add https://github.com/acartag7/edictum --skill update-docs-acartag7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syncs documentation with code changes so PRs stay accurate and consistent, reducing drift between code and docs.

Core Features & Use Cases

  • Maps changed source files to the relevant docs pages and surfaces suggested updates during PRs.
  • Enforces frontmatter presence and style guidelines to maintain consistency across docs.
  • Use Case: When a PR touches library code, ensures docs reflect new APIs and architectural changes with minimal manual edits.

Quick Start

Run git diff main...HEAD --name-only to identify changes and map them to documentation updates.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I keep documentation in sync with code changes across pull requests?

To keep documentation in sync with code changes, map modified source files to their corresponding docs pages and enforce frontmatter and style guidelines to propose updates automatically during PR workflows.

What is the best way to automate documentation updates when library code changes?

Automating documentation updates involves running a deterministic workflow that detects changed files via git diff, maps them to relevant documentation pages, and applies corrections to reflect new APIs and architectural changes.

How do I enforce yaml-frontmatter and style guide compliance in docs?

Enforce yaml-frontmatter and style guide compliance by validating documentation pages during the pull request workflow, ensuring that proposed or applied updates adhere to the project's specific frontmatter requirements and formatting rules.

Does this docs-sync workflow require specific prerequisites to map source files?

The docs-sync workflow requires a project with established frontmatter requirements and style guidelines, using a deterministic workflow to map code changes across multiple source files to their corresponding documentation corrections.

Can I surface suggested documentation corrections directly during a pull request?

Yes, you can surface suggested documentation corrections directly during a pull request by detecting changed files and mapping those source changes to the relevant documentation pages for immediate review.

What are the limitations of using a deterministic workflow for mapping code to docs?

The limitation of a deterministic workflow for mapping code to docs is that it requires strict adherence to predefined frontmatter and style guidelines, meaning non-standard or unmapped source files may not receive automated documentation updates.