skills.rest
AntonBespalov
AntonBespalovCOMMUNITY
Explore all skills by this author →
GitHub

docs-maintainer

Identify document owners and truth sources impacted by code changes.

Updated Jan 30, 2026
Search Tags:#documentation#consistency#ownership#governance#diff#change-management
One-click install
npx skills add https://github.com/AntonBespalov/WC_IST --skill docs-maintainer-antonbespalov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-maintainer
Source: https://github.com/AntonBespalov/WC_IST/tree/main/.codex/skills/docs-maintainer
Command: npx skills add https://github.com/AntonBespalov/WC_IST --skill docs-maintainer-antonbespalov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps documentation aligned with code changes by identifying document owners and canonical sources of truth that require updates after features, refactors, or patch finalization.

Core Features & Use Cases

  • Owner mapping: maps changes to responsible documentation owners and canonical sources of truth.
  • Impact analysis: highlights affected documents and sections that need synchronization.
  • Guidance for PRs: provides a checklist of docs to update before merging.

Quick Start

After applying a feature or refactor, identify affected documents and owners and produce a diff highlighting what needs updating.

Frequently Asked Questions about docs-maintainer

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

FAQPage Schema
How do I keep documentation in sync after code changes?▼

To keep documentation in sync after code changes, you need to identify impacted documents and owners, then produce a diff highlighting what needs updating before merging your refactor or patch.

What is the best way to find document owners for a codebase refactor?▼

Finding document owners for a codebase refactor requires mapping changes to responsible documentation owners and canonical sources of truth to ensure governance and accountability during updates.

How do I identify which canonical sources of truth require updates after a patch?▼

To identify which canonical sources of truth require updates after a patch, perform an impact analysis that highlights affected documents and sections needing synchronization when contracts or architecture boundaries change.

Do I need to update documentation before merging a pull request?▼

Yes, you need to update documentation before merging a pull request by generating a checklist of impacted docs and a diff to guide synchronization, ensuring consistency between code and docs.

When should I perform documentation impact analysis during change management?▼

You should perform documentation impact analysis during change management after feature implementation, refactoring, or patch finalization when safety, timings, contracts, or architecture boundaries change.

Can I generate a diff of impacted documents after finalizing a feature implementation?▼

Yes, you can generate a diff of impacted documents after finalizing a feature implementation to guide synchronization and maintain consistency across all affected canonical sources of truth.

Related Skills

Explore More Content & Communication Skills→
thesyntaxninjathesyntaxninja
2

self-review

Review git diffs for deletions, simplifications, and pattern mismatches.

Community
Intermediate
burgebjburgebj

document-release

Parse Git diff outputs to update Markdown documents after releases.

Community
Intermediate
giljaegiljae
1

gstack-review

Analyze pull request code diffs for structural issues, scope creep, and test coverage.

Community
Advanced
dt418dt418

Docs Pack

Build documentation platforms with versioned docs, search, navigation, code highlighting, and API reference generation.

Community
Intermediate