herdr-pre-release-audit
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.
git clone --depth 1 https://github.com/herdrdev/herdr /tmp/herdr-pre-release-audit && cp -r /tmp/herdr-pre-release-audit/.agents/skills/herdr-pre-release-audit ~/.claude/skills/herdr-pre-release-auditSKILL.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.
Create and control a disposable named Herdr session from inside an existing Herdr session. Use for isolated Herdr runtime, pane, terminal, process, API, persistence, or agent reproductions that should be driven through the CLI/API without touching the default session.
Triage open herdr GitHub issues into a concise decision-first Markdown table. Use when the user says "triage", asks to triage open issues, asks which issues need attention, or wants issue priority/recommendation lights for herdr.
Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires HERDR_ENV=1.
>-