doc

Identify documentation gaps from code changes and propose precise doc updates.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/remiboivin021/synexis --skill doc-remiboivin021
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc
Source: https://github.com/remiboivin021/synexis/tree/main/.agents/skills/doc
Command: npx skills add https://github.com/remiboivin021/synexis --skill doc-remiboivin021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation drift and misalignment with code and governance contracts slow down development and erode trust in project docs. This skill helps you update, validate, and align documentation with the current codebase and ADRs.

Core Features & Use Cases

  • Documentation updates: Propose precise edits that reflect recent changes in code, ADRs, and governance.
  • Validation & integrity: Check that docs stay aligned with implemented behavior, configs, and CLI contracts.
  • Use Case: When a feature lands, generate a maintainable doc draft that captures behavior, usage, and references.

Quick Start

Provide a ready-to-use documentation draft that reflects the latest changes in the repository.

Frequently Asked Questions about doc

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

FAQPage Schema
How do I identify documentation gaps introduced by recent code changes?

To identify documentation gaps from recent code changes, analyze feature behavior, configuration contracts, CLI entrypoints, and data models against existing docs to propose precise, implementation-aligned updates.

What is the best way to maintain architecture decision records when features change?

Maintaining architecture decision records during feature changes requires validating governance ADRs against the updated codebase to ensure documentation stays aligned with current implementation and repository scope.

How do I generate a review-ready documentation draft after a feature lands?

Generate a review-ready documentation draft by capturing new feature behavior, usage instructions, and references directly from recent repository changes while constraining the scope to current implementation.

Can I validate configuration contracts and CLI entrypoints against existing documentation?

You can validate configuration contracts and CLI entrypoints by checking that existing documentation stays aligned with implemented behavior and repository scope to prevent documentation drift.

What causes documentation drift and how do I prevent misalignment with code contracts?

Documentation drift is caused by code or contract changes outpacing documentation updates, which you prevent by proposing precise edits that align feature behavior and governance docs with the current codebase.