Map branch diffs to affected documentation using configured doc schemas.
npx skills add https://github.com/jackneil/claude-jacked --skill docs-sync-jackneil
Please help me install this Agent Skill. Skill: docs-sync Source: https://github.com/jackneil/claude-jacked/tree/main/jacked/data/skills/docs-sync Command: npx skills add https://github.com/jackneil/claude-jacked --skill docs-sync-jackneil
Documentation drift occurs when code changes outpace docs; this skill helps ensure docs stay accurate by mapping code diffs to affected docs during PRs.
Run the docs-sync skill on your feature branch to generate a diff-aligned set of documentation updates.
High-intent search queries and answers about installing and using this skill.
To keep documentation aligned with code changes, you can diff your current branch against the base and map the changes to affected docs. This ensures docs stay accurate by associating code diffs with the correct documents during feature completion or PRs.
You should sync docs with code refactoring updates ahead of PRs or immediately after the refactor completes. Mapping repository diffs to configured doc schemas during these stages prevents documentation drift across the project.
Mapping code diffs to documentation works by comparing the current branch against the base branch and relying on configured doc schemas. It associates the detected code changes with the right documents to generate a diff-aligned set of documentation updates.
Yes, you can use it for PR workflow documentation maintenance by running it on your feature branch. It applies during feature completion to automatically align corresponding docs with code changes before submitting a pull request.
The best way to update module docs after a code change is to run a diff against the base branch. This automatically aligns corresponding documentation with the module changes by mapping repository diffs to the configured doc schemas.
toinfinityaiAnalyze source code diffs against main and update mapped documentation pages.
camronhGenerate a merge-prep plan with documentation and changelog updates.
windmill-labsCreate draft GitHub pull requests with conventional commit titles.
galatanovidiuIdentify and update documentation affected by code changes during the docs phase.
