gen-docs

Update CLI user documentation from git commits, staged changes, and changelogs.

6|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Wyl-cmd/kxns-cli --skill gen-docs-wyl-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-docs
Source: https://github.com/Wyl-cmd/kxns-cli/tree/main/.agents/skills/gen-docs
Command: npx skills add https://github.com/Wyl-cmd/kxns-cli --skill gen-docs-wyl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping user documentation in sync with a fast-changing codebase is tedious and error-prone. This Skill reviews recent git commits, staged changes, and changelog entries to detect how product behavior actually changed, then updates the docs directory page by page so the documentation always matches the real user experience. ## Core Features & Use Cases - Change-Driven Doc Updates: Reads recent git commits, staged changes, and changelog.md to identify user-facing behavior changes, consulting the actual source code when needed. - Changelog Synchronization: Runs the docs/scripts/sync-changelog.mjs script first to keep the English changelog current before editing content. - Bilingual Documentation Maintenance: Verifies Chinese documentation matches the latest code behavior, then hands off to the translate-docs skill for bilingual synchronization. - Use Case: After merging a feature branch that changes CLI flags, invoke this Skill to audit every affected docs page against the new code and produce consistent, up-to-date English and Chinese documentation. ## Quick Start Update the project documentation to reflect the latest git commits and staged changes, then sync the changelog and translations.

Frequently Asked Questions about gen-docs

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

FAQPage Schema
How do I keep CLI documentation in sync with code changes?

Review recent git commits, staged changes, and changelog entries to identify user-facing behavior changes, then update each affected documentation page against the actual source code. This Skill automates that audit page by page.

How to update documentation after merging a feature branch?

Run the documentation update workflow right after merging: it inspects the new commits, verifies behavior against the real code, syncs the English changelog with the sync-changelog script, and updates the Chinese docs before translation.

Does this documentation workflow support bilingual docs?

Yes. It first ensures the Chinese documentation matches the latest code behavior, then delegates to the translate-docs skill to synchronize the English and Chinese versions.

What inputs does the documentation update process need?

It needs access to the repository's git history, staged changes, changelog.md, the docs directory with its AGENTS.md guidelines, and the actual source code to verify real behavior changes.

Why does the changelog need to be synced before editing docs?

Syncing the English changelog first with docs/scripts/sync-changelog.mjs establishes an authoritative record of changes, so subsequent documentation edits are grounded in an accurate, ordered list of what actually changed.