Detect code changes via git diff and update affected documentation surfaces.
npx skills add https://github.com/Nymbo/Skills --skill docs-sync-nymbo
Please help me install this Agent Skill. Skill: docs-sync Source: https://github.com/Nymbo/Skills/tree/main/docs-sync Command: npx skills add https://github.com/Nymbo/Skills --skill docs-sync-nymbo
Keeps documentation surfaces aligned with code changes across README, docs sites, API docs, runbooks, and configuration. Use when the user asks to update docs, ensure docs match behavior, or prepare docs for a release/PR.
After code changes, run the docs-sync workflow to update the affected docs surfaces and verify with a docs build.
High-intent search queries and answers about installing and using this skill.
Docs-sync detects code changes via git diff, identifies affected documentation surfaces like README and API specs, and applies targeted updates to keep implementation and docs aligned. Run the workflow after code changes to automatically update relevant docs and verify consistency.
Documentation sync covers README files, docs/ directories, wiki pages, API specifications, changelogs, and runbooks. The Skill scans these common surfaces, maps code changes to impacted docs, and updates environment variables, API contracts, database migrations, and architectural decisions across all of them.
Yes. Docs-sync includes verification steps that validate docs builds and check link integrity after updates. Linting and build checks enforce consistency between documentation and implementation, catching mismatches before release or PR merge.
The Skill analyzes git diffs to detect changed files, maps those changes to documentation surfaces, and creates an inventory of impacted docs. It then determines which sections need updates based on the code changes—such as API contracts, environment variables, or setup instructions.
Use docs-sync after code changes, during feature releases, before merging PRs, or when preparing for deployment. It ensures README, API docs, runbooks, and changelogs reflect actual implementation, preventing user confusion from outdated documentation.
Yes. Docs-sync handles markdown files in README and docs/ directories alongside API specifications and other documentation formats. It applies templates and consistency rules across all surfaces to maintain alignment with code changes.
stas-kaSynchronize repository documentation with code changes and version bumps.
remix-runCreate or update Remix repo change files under packages/*/.changes.
adtecoRun type checks, linting, builds, tests, and security scans before commits.
icartshGenerate READMEs, changelogs, and API references from Git history.
