Sync repository documentation using git change signals and a declared focus.
npx skills add https://github.com/hollis-labs/volon --skill docs-sync-hollis-labs
Please help me install this Agent Skill. Skill: docs-sync Source: https://github.com/hollis-labs/volon/tree/main/plugins/docsmith/skills/docs-sync Command: npx skills add https://github.com/hollis-labs/volon --skill docs-sync-hollis-labs
Prevents documentation drift by applying minimal, verifiable updates to repository docs based on concrete change signals and a focused scope, ensuring docs remain accurate without inventing facts.
Run docs-sync with an appropriate focus (user|dev|feature|release|all), include slug when focus=feature, and set pr=auto to request a PR if desired.
High-intent search queries and answers about installing and using this skill.
To keep repository documentation in sync with git changes, this Skill reads git status, diff, and log outputs to apply minimal, verifiable edits to README, docs, and CHANGELOG files. It only updates intersecting target sections based on concrete change signals.
The best way to update README and docs after code modifications is using a focus-driven sync tool. You provide a focus argument like user, dev, or feature, and the tool applies section-level minimal diffs only where changed components are referenced.
You prevent documentation drift by applying minimal, accurate diffs driven by git change signals and a declared focus. This ensures docs remain accurate without inventing facts, marking any unverifiable information as TBD during the update.
Yes, you can automatically open a PR after updating repository documentation. By setting pr=auto, the tool optionally opens a pull request according to the repository git.pr_mode settings after running pcc-refresh to keep the context cache consistent.
Yes, updating SKILL.md description lines requires dev mode. The documentation sync process restricts SKILL.md edits to dev mode only, while standard README, docs, and CHANGELOG updates occur during targeted reviews or when git reports related file changes.
A limitation of using git change signals for documentation updates is that facts not verifiable from the diffs or logs are marked TBD rather than invented. Additionally, updates are scoped strictly to intersecting target sections, leaving out-of-scope documentation untouched.
K-h-HuangSummarize git working tree changes and draft three Conventional Commit messages.
dolsoonDiscover, retrieve, and cache documentation based on user intent and project context.
ex3ndrManage multi-agent development workflows with Git operations and pull request generation.
incubrainGenerate Nuxt UI component Markdown documentation from the official repository.
