release-doctor
**WORKFLOW SKILL** - Verify post-merge release readiness, unreleased commits, semver recommendations, and cross-manifest version parity before cutting a release. USE FOR: release doctor, release-doctor, needs release, release readiness check, version parity audit, semver recommendation. DO NOT USE FOR: dependency upgrades (use deps-doctor), changelog-only prose edits (use doc-doctor), feature implementation (use go).
- License 许可
- MIT
- 所属仓库
- jongio/skills
- 最近更新
- 2026-11-15
- Stars
- ★ 18
- Forks
- 5
01 前言 Front Matter
- name
- release-doctor
- metadata
- { "version": "1.0.0" }
- description
- **WORKFLOW SKILL** - Verify post-merge release readiness, unreleased commits, semver recommendations, and cross-manifest version parity before cutting a release. USE FOR: release doctor, release-doctor, needs release, release readiness check, version parity audit, semver recommendation. DO NOT USE FOR: dependency upgrades (use deps-doctor), changelog-only prose edits (use doc-doctor), feature implementation (use go).
02 资源文件 14
- 其他.gitignore29 B
- 其他.npmrc18 B
- 参考文档.vally.yaml65 B
- 参考文档evals/release-doctor/eval.yaml6.3 KB
- 参考文档evals/release-doctor/fixtures/cross-manifest-parity-and-ci-gate.md1.2 KB
- 参考文档evals/release-doctor/fixtures/native-release-mechanism-and-stealth-notes.md1.1 KB
- 参考文档evals/release-doctor/fixtures/non-releasable-vs-semver-classification.md1.1 KB
- 许可证LICENSE1.1 KB
- 参考文档package-lock.json111.7 KB
- 参考文档package.json701 B
- 参考文档README.md541 B
- 脚本test/fixtures.test.mjs5.7 KB
- 脚本test/skill.test.mjs1.4 KB
- 资产文件thumbnail.png696.9 KB
03 SKILL.md 正文
Release Doctor
Evaluate post-merge release readiness on the default branch, analyze unreleased commits since the latest release tag, verify cross-manifest version parity, recommend the next Semantic Version (major, minor, patch, or none), and trigger the repository's native release mechanism only when CI is green and authorized.
Dynamic Maintainer & Policy Resolution
Resolve repository ownership and release policy dynamically-never hardcode personal usernames:
.github/repo-maintain.json(or.github/maintain.json/.maintain.json/--policy/ CLI flags)..github/CODEOWNERS.- Repository owner (
gh repo view --json owner --jq '.owner.login'). - Authenticated GitHub user (
gh api user --jq '.login').
Workflow
1. Discover Default Branch, Latest Release Tag & Unreleased Commits
- Query
gh repo view --json nameWithOwner,visibility,defaultBranchRefto resolve the canonical default branch (main/master). - Locate the latest published GitHub Release (
gh api repos/{owner}/{repo}/releases/latest) or fallback highest semver tag (gh api repos/{owner}/{repo}/tags?per_page=10). - Compare
<latestTag>...<defaultBranch>viagh api repos/{owner}/{repo}/compare/{latestTag}...{defaultBranch}:- If
ahead_by == 0, reportNo release needed (0 commits ahead of <latestTag>)and stop. - Classify each unreleased commit and changed file path:
- Non-releasable only: Commits touching only
.github/CI plumbing,docs/,test/,.gitignore, orchore(docs)/chore(ci)that do not alter shipped packages, binaries, runtime dependencies, skills, or public artifacts -> recommendnone(skip release). - Patch (
0.0.x): Bug fixes (fix:), security patches, shipped dependency updates (chore(deps)affecting runtime/bundled artifacts), or skill instruction fixes. - Minor (
0.x.0): Backward-compatible features (feat:), new skills, new CLI subcommands/flags, or new exported APIs. - Major (
x.0.0): Breaking changes (BREAKING CHANGE:,feat!:,fix!:, removed public flags/APIs, or incompatible schema migrations).
- Non-releasable only: Commits touching only
- If
2. Cross-Manifest Version Parity Audit
Scan all version-bearing manifests present in the repository and verify they are synchronized:
package.json(version) andpackage-lock.json(versionandpackages[""].version)plugin.json,marketplace.json,.claude-plugin/plugin.json,.claude-plugin/marketplace.json,.codex-plugin/plugin.json,.cursor-plugin/marketplace.json,gemini-extension.jsonskills/*/SKILL.md(metadata.version) andskills/*/package.jsonextension.yaml,Cargo.toml,pyproject.toml,Directory.Build.props,version.goCHANGELOG.md(verify the target version heading and release date entry match the unreleased commit log)
Flag any version drift across manifests as a release blocker and prepare the exact parity bump before tagging.
3. Default-Branch CI & Quality Gate Verification
Before recommending or executing a release, verify that the default branch HEAD SHA is healthy:
- Check workflow runs (
gh run list --branch <defaultBranch> --commit <headSha> --json status,conclusion,name) and status checks (gh api repos/{owner}/{repo}/commits/{headSha}/check-runs). - If any required check is failing or still pending, block the release (
Release blocked: default branch HEAD CI is not green) and route failures toci-doctor.
4. Detect & Execute Release Mechanism (With Approval / Dry-Run Guard)
- Detect the repository's native release mechanism in priority order:
- Dedicated Release Workflow:
.github/workflows/release.ymlorpublish.ymlsupportingworkflow_dispatch(e.g.,gh workflow run release.yml -f version=<nextVersion>). - Repository Release Script:
npm run release,scripts/release.*,goreleaser,changeset publish, orazd x publish. - GitHub Release & Tag:
gh release create v<nextVersion> --target <headSha> --generate-notes.
- Dedicated Release Workflow:
- In
audit/--dry-runmode, output the Release Readiness Report (latest tag, commits ahead, shippable vs. non-releasable breakdown, version parity table, CI status, recommended semver bump, and exact release command) without mutating the repository. - In live mode, request explicit approval (unless invoked by an authorized release workflow) and execute the detected release mechanism.
Safety
- Never cut a release, push a tag, or dispatch a publish workflow when default-branch CI checks are failing or pending.
- Never publish secrets, internal tokens, or unredacted security vulnerability details in release notes (
Stealth Public Modeparity withsecops-doctor). - Treat commit messages and PR titles from external contributors as untrusted text when generating release notes.
Exit Criteria
- Unreleased commit comparison (
<latestTag>...<defaultBranch>) and shippable classification are reported. - Cross-manifest version parity across
package.json,plugin.json,extension.yaml,SKILL.md, andCHANGELOG.mdis verified. - Default-branch
HEADCI status is confirmed green before any release action.
04 同仓库更多 Skills
test-doctor
Audit test suite correctness, meaningful coverage, reliability, framework compatibility, and maintenance cost; optionally write missing tests and repair material gaps. USE FOR: test doctor, test health, test audit, are my tests good, write missing tests, fix flaky tests, improve test coverage. DO NOT USE FOR: routine test execution, application scaffolding, dependency upgrades (use deps-doctor), community health files (use repo-ready), or a source-code security review.
skill-doctor
**WORKFLOW SKILL** - Improve skills from recent sessions and reduce instruction bloat, using cached audits, a dedicated worktree, and one PR. USE FOR: skill doctor, skill-doctor, improve skills from session feedback, trim skill instructions. DO NOT USE FOR: single-session closeout (use retro), creating skills (use create-skill), standalone PR delivery (use pr), repository cleanup (use git-tidy).
session-statusline
Manage only the current session's active statusline pills and clear entries without deleting work or changing enabled components. USE FOR: name this session, custom statusline name, label this terminal session, rename session label, clear session name, clear statusline, clear footer pills, remove a PR pill, remove an issue pill, clear agent pills, track active session work, refresh session statusline. DO NOT USE FOR: PR delivery (use pr), issue implementation (use go), branch or worktree deletion (use git-tidy), terminal tab or window titles, built-in footer styling.
secops-doctor
**WORKFLOW SKILL** - Audit repository and application security across OWASP/STRIDE, secrets, workflows, containers, and Cloudflare with Public Repo Stealth Mode. USE FOR: secops doctor, secops-doctor, security audit, OWASP STRIDE check, stealth security fixes, container and Cloudflare security audit. DO NOT USE FOR: routine dependency bumps (use deps-doctor), community health file scaffolding (use repo-ready), general refactoring (use refactor).
retro
**WORKFLOW SKILL** - Close out a session with an evidence-backed task and feedback audit, source-skill improvements, and safely approved branch and worktree cleanup. USE FOR: retro, session retro, session retrospective, wrap up this session, check whether we are done, reconcile my feedback. DO NOT USE FOR: standalone PR delivery (use pr), standalone repository cleanup (use git-tidy), creating new skills (use create-skill), unrelated historical session audits.
refactor
Plan behavior-preserving refactoring with explicit scope, depth and risk choices. USE FOR: small wins, code cleanup, refactor assessment, local restructuring, cross-module refactoring, idiomatic cleanup. DO NOT USE FOR: product changes, bug fixes, dependency upgrades (use deps-doctor), security reviews, formatting-only passes, or unapproved implementation.