Update developer-facing documentation from an explicit list of changed files.
npx skills add https://github.com/wp-media/imagify-plugin --skill docs-wp-media
Please help me install this Agent Skill. Skill: docs Source: https://github.com/wp-media/imagify-plugin/tree/main/.claude/skills/docs Command: npx skills add https://github.com/wp-media/imagify-plugin --skill docs-wp-media
Updating internal developer documentation to reflect code changes on the current branch is error-prone and time-consuming if done manually, leading to out-of-sync docs and miscommunication across teams.
Run the docs skill to produce updated developer-facing docs for the current branch changes.
High-intent search queries and answers about installing and using this skill.
To keep developer documentation in sync, you can use a workflow that consumes an explicit list of changed files and outputs updated docs to reflect code changes on the current branch. This prevents out-of-sync documentation.
Automating internal docs updates involves flagging code or configuration changes on the working branch and producing updated developer-facing documentation. This reduces manual overhead and improves onboarding accuracy.
No, the documentation update workflow does not infer scope from git automatically. It requires an explicit list of changed files as input to determine which developer docs need alignment with the code.
Yes, you can use this documentation workflow in your CI pipeline. It is designed for CI or local development workflows, consuming an explicit list of changed files to output updated docs without inferring scope from git.
You need to update developer-facing documentation when configuration or code changes are flagged for the current branch and require alignment. This ensures accurate project docs and reduces miscommunication across teams.
RxFitUpdate README, Architecture, Contributing, and Change Log files using git diff.
PacificStudioEnforce CI and branch-state checks before merging Git changes.
jimmymalhanScan git diffs for secrets, injection flaws, and PII exposure.
carayaResolve editorial style decisions using Google developer documentation style with Chicago Manual of Style fallback.
