skills.rest
Vasallo94
Vasallo94COMMUNITY
Explore all skills by this author →
GitHub

Documentation Updater

Synchronize project documentation with code changes across specified doc paths.

8|1|Updated Jun 30, 2025
Search Tags:#architecture#templates#documentation#docs#checklists#CHANGELOG#tool-reference
One-click install
npx skills add https://github.com/Vasallo94/obsidian-mcp-server --skill documentation-updater-vasallo94
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Documentation Updater
Source: https://github.com/Vasallo94/obsidian-mcp-server/tree/main/.agent/skills/docs-updater
Command: npx skills add https://github.com/Vasallo94/obsidian-mcp-server --skill documentation-updater-vasallo94

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill keeps project documentation synchronized with code changes to prevent drift.

Core Features & Use Cases

  • Maintains standardized documentation templates and structures across the repository
  • Updates critical docs sections automatically (docs/tool-reference.md, docs/architecture.md, CHANGELOG.md)
  • Provides checklists and guidelines to ensure documentation stays current

Quick Start

Use this skill to align your repository's documentation with code changes. For example, when you add a new MCP tool, run Documentation Updater to update docs/tool-reference.md and CHANGELOG.md.

Frequently Asked Questions about Documentation Updater

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

FAQPage Schema
How do I keep documentation synchronized with code changes to prevent drift?▼

Documentation drift is prevented by applying standardized templates and checklists that update architecture, tool-reference, and configuration sections whenever code changes occur.

What is the best way to update architecture and configuration docs after adding a new tool?▼

The best way to update architecture and configuration docs is using a standardized documentation structure that guides updates via checklists, ensuring docs/architecture.md and docs/tool-reference.md stay aligned with the new tool.

When do I need to update my project's CHANGELOG.md and tool-reference documentation?▼

You need to update CHANGELOG.md and tool-reference documentation when adding new tools, updating configurations, or changing architecture to ensure repository docs stay aligned with code modifications.

Does this documentation update approach work without external dependencies?▼

Yes, this documentation update approach works without external dependencies, relying solely on standardized templates, checklists, and specific docs paths like docs/architecture.md and CHANGELOG.md to maintain structure.

How do I enforce a standardized documentation structure across my repository?▼

You enforce a standardized documentation structure by applying checklists and templates that guide updates across tool-reference, architecture, and configuration sections, ensuring consistent docs alignment with code.

Related Skills

Explore More Software Engineering Skills→
steven-3steven-3

supermind-living-docs

Synchronize ARCHITECTURE.md and DESIGN.md with repository changes using git diff.

Community
Intermediate
alexandrbasisalexandrbasis
12

udoc

Update project documentation and generate changelog entries from completed tasks.

Community
Intermediate
hoklimshoklims

oco-verify-fix

Run build, type, lint, and test commands to validate code changes.

Community
Advanced
phuthuycodingphuthuycoding
10

documentation

Generate README, API, and architecture documentation from code scans.

Community
Basic