Skip to content
Back to skills

Review Public Docs

ASecurity

Review the shipped prose, site pages and release notes before a release. Load by path.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 21, 2026
development

Security analysis

A100/100

Scanned October 21, 2026

npx -y skills add gwpicard/ai-build-kit --skill review-public-docs --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Review Public Docs?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Review Public Docs
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gwpicard-review-public-docs/badge)](https://www.skillsdirectory.com/skills/gwpicard-review-public-docs)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: review-public-docs
description: Review the shipped prose, site pages and release notes before a release. Load by path.
---

# Review public docs

Run before preparing a release. Read the release allowlist, then split the
shipped prose, site pages and release notes draft into about five parts. Include
the relevant source files with each part.

Give each part to a fresh reviewer that has not seen another review. Ask it to
check claims in this order: code and checks, release notes, then the inventory.
Look for stale terms, contradictions, wrong counts, broken references and
unsupported claims. A reviewer must confirm each finding in the code or check
before reporting it. Otherwise it reports the concern as unconfirmed.

Collect the reports in `.agents/tmp/public-docs-review/` and combine confirmed
findings into one list for the maintainer. A release waits until each finding
is fixed or the maintainer accepts it. Keep accepted findings and their reasons
with the review record.

## The printout

One line for each finding, most serious first:
`file:line` | kind (stale, contradiction, count, reference, unsupported) |
what the code or check shows, with its `file:line` | the fix in one line |
confirmed or unconfirmed.

Under the list, give the count of each kind and the findings the maintainer
already accepted, with the reason. This review reports and changes nothing.

## Done when

Every part has had one fresh reviewer, every confirmed finding is on the list,
and the maintainer has fixed or accepted each one before the release is
prepared.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.