agentsclimarketplace

Docs drift review

Skill yarlson/yarstack/plugins/yarstack/skills/docs-drift-review

Engineering workflows and standards for Codex and Claude Code: plan, implement, test, review, and deliver repository changes.

Install
npx -y skills add yarlson/yarstack --skill docs-drift-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review documentation for drift caused by the current code or configuration change. Use to identify concrete inaccuracies and, when authorized, repair only directly affected documentation.

SKILL.md

1.6 KB, as published. Nobody here has run it

Documentation Drift Review

Own change-scoped documentation accuracy through separate inspection and repair stages.

Workflow

  1. Confirm the changed behavior and whether the task authorizes documentation edits or only a read-only drift report.
  2. Identify canonical, generated, mirrored, and external documentation describing the changed surface.
  3. Compare implementation with README files, instructions, APIs, schemas, operational docs, examples, templates, and command help in scope.
  4. Report concrete drift with the affected claim, implementation evidence, canonical owner, and required correction.
  5. When edits are authorized, update only directly affected canonical documents in their existing style.
  6. Change generated documentation or help at its source and regenerate it through the repository's established command.
  7. For authorized prose edits, use english-text-review on the final changed text and apply material findings without expanding the drift scope.

Use docs-review for broader documentation quality, repo-context-document for deliberate docs/context/ work, plan-update for plan mechanics, and spec-update for semantic contract decisions.

Do not restructure documentation, hand-edit generated content, change product behavior, or modify external documentation without authority.

Finish with changed documents, an evidenced no-change result, or unresolved owner decisions.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.