agentsclimarketplace

Tidy docs

Skill chrisallenlane/claude-swe-workflows/skills/tidy-docs

Mechanical documentation hygiene. Spawns a doc-maintainer agent to audit all project documentation and fix correctness, completeness, freshness, and consistency issues autonomously within its authority. Surfaces anything requiring user judgment for approval.From its SKILL.md

Install
npx -y skills add chrisallenlane/claude-swe-workflows --skill tidy-docs

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

  • 18 stars18 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.

SKILL.md

1.8 KB, 350 tokens by cl100k_base, as published. Nobody here has run it

Tidy-Docs - Documentation Hygiene

Spawns a doc-maintainer agent to comprehensively audit all project documentation and fix the issues it finds. The find→fix seam is small — typos, stale code examples, broken links, freshness drift — so the skill runs as a tidy rather than a review.

Workflow

1. Spawn doc-maintainer agent

Spawn a DOC - Maintainer agent with the following prompt:

Perform a comprehensive review of ALL project documentation. This is a
standalone audit — do NOT scope to git diff. Instead, review every
documentation file in the project.

Steps:
1. Discover all documentation files (README.md, CLAUDE.md, CONTRIBUTING.md,
   CHANGELOG.md, doc/, docs/, adr/, and any other .md files)
2. Review each for correctness, completeness, and freshness using your
   full quality checklist (code-documentation consistency, completeness,
   link validation, style consistency, freshness)
3. Fix issues you find autonomously (within your authority)
4. Report what you changed and any issues requiring user approval

If no documentation issues are found, report that and exit.

2. Report results

After the agent completes, present its findings to the user:

  • What was reviewed
  • What was changed (if anything)
  • Issues requiring user approval (if any)

3. Commit (optional)

If changes were made, ask the user if they want to commit. If yes:

git add [specific files]
git commit -m "$(cat <<'EOF'
docs: tidy project documentation

[Brief description of changes made]
EOF
)"

What ships with it: 1 file

4.3 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,835. 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.