herdrdev/herdr

herdr-pre-release-audit

Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs.

Trending #6494 Hot #1832 First seen Jul 9, 2026

Installation

$ npx skills add herdrdev/herdr --skill herdr-pre-release-audit

Summary

  • Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs.
  • Use when asked to run or apply the repo's pre-release audit, validate docs/next before release, inspect issue refs that release CI will close, or finalize release docs for herdr.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from herdrdev/herdr.

npx skills add herdrdev/herdr

Browse all from herdrdev/herdr

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 36.7K
License LICENSE
Default branch master
Open issues 285
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,154 B
  • docs SUMMARY.md 324 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 430 installs

SKILL.md

Herdr Pre-release Audit

Use this skill only inside the herdr repository.

Read references/pre-release-audit.md and follow its workflow. Treat it as the source of truth for:

  • choosing the release base ref
  • inspecting first-parent history and merged PRs
  • auditing docs/next/CHANGELOG.md
  • auditing docs/next/README.md and staged website docs
  • checking skills/herdr/SKILL.md against shipped CLI and agent-control behavior
  • checking issue reference lines
  • deciding when to run just pre-release-check or its component checks
  • running and assessing just bench-render-scale
  • producing the final release-readiness report

Do not edit files during the audit unless the user explicitly asks to apply fixes. When applying fixes, keep changes scoped to the files named in the reference workflow.