agentsclimarketplace

Docs review

Skill yarlson/yarstack/plugins/yarstack/skills/docs-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-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

Audit or improve general repository documentation against implemented behavior. Use for deliberate README or documentation-quality work not owned by a more specific documentation skill.

SKILL.md

1.6 KB, as published. Nobody here has run it

Documentation Review

Own general repository-document quality in an explicit audit-only or authorized edit mode.

Workflow

  1. Confirm audience, document set, desired outcome, and whether the task authorizes edits.
  2. Route current-change drift to docs-drift-review, docs/context/ structure to repo-context-document, semantic contracts to spec-update, journeys to critical-journey-document, and persuasive claims to marketing-claims-review.
  3. Verify content against implementation, commands, configuration, examples, tests, metadata, and canonical documents.
  4. Classify evidence-backed findings as keep, update, merge, split, move, archive, or remove.
  5. In audit-only mode, return prioritized findings without edits.
  6. In edit mode, change only the confirmed document set and preserve repository structure and voice unless that structure is the requested defect.
  7. Use english-text-review on changed prose and apply its material findings without changing verified facts, required terminology, or intentional voice.
  8. Require explicit authority before archiving, removing, or materially expanding the document set.

Do not invent features, commands, architecture, benchmarks, screenshots, promises, or roadmap items; impose a generic template; or broaden a focused request.

Finish with an evidence-backed audit or verified scoped edits, plus unresolved facts needing an owner.

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.