AGENT SKILL

release-check

Use when cutting an Orchard release (tagging a new version of the FastAPI inventory service) — walks the pre-tag checklist so migrations, verify, changelog, and the tag stay in sync.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 152
Forks
7

01 前言 Front Matter

name
release-check
description
Use when cutting an Orchard release (tagging a new version of the FastAPI inventory service) — walks the pre-tag checklist so migrations, verify, changelog, and the tag stay in sync.

03 SKILL.md 正文

Release Check — Orchard

Cutting a release for Orchard is mechanical but easy to half-do (tag without the migration check, bump the version but forget the changelog). This skill is the checklist so nothing slips. It loads only when you're releasing — everyday work doesn't pay for it.

When this fires

You type /release-check, or you're about to tag a new Orchard version.

Checklist

Walk these in order. Stop at the first failure, fix it, restart — a release is atomic.

  1. Clean tree, right branch. git status is clean and you're on main (or the release branch). No uncommitted work rides along in a tag.
  2. Bump the version. Update version in pyproject.toml. Use semver: breaking API/contract change → major; new endpoint/field → minor; fix only → patch.
  3. Migrations present and current. alembic check is clean (no model-vs-history drift), and every new revision has been applied once against a dump of representative data, not just an empty DB. alembic check proves agreement, not applicability — this step proves applicability.
  4. Verify is green. Run scripts/verify.sh and read the output: format, lint, types, migrations, test all pass. Within-a-layer green only — also confirm one real request path (TestClient against the full app) still works end to end.
  5. Changelog updated. Add a dated section to CHANGELOG.md for this version: what changed, and call out any API-contract or migration change explicitly so callers know to look.
  6. Commit, then tag. chore(release): vX.Y.Z commit, then git tag vX.Y.Z. Tag points at the release commit — never an earlier one.
  7. Push commit and tag. git push && git push --tags. Open/reference the GitHub release.

Notes

  • If alembic check fails, you have a model change with no migration — that's a code bug, not a release step. Go back and add the revision before tagging.
  • Don't allowlist a secret to make a hook pass; the no-secrets rule is absolute (core).

04 同仓库更多 Skills

PromptPartner
PromptPartner/agentsmith

portable-fixture

Fixture proving that skill identity comes from metadata rather than its installation path.

★ 152
PromptPartner
PromptPartner/agentsmith

portable-fixture

Fixture proving that skill identity comes from metadata rather than its installation path.

★ 152
PromptPartner
PromptPartner/agentsmith

writing-rules

Write or review anything an agent reads — a core rule, a profile gate, a SKILL.md description, an instruction-file line, a subagent prompt, a handoff note, a verify-phase label. Part of the Agentsmith harness; supplies the levers that decide whether a line changes behaviour or only costs tokens — the two loads, context pointers, the ladder, completion criteria, leading words, the no-op test. Its default move is deletion, so it earns most on a draft that already exists.

★ 152
PromptPartner
PromptPartner/agentsmith

wayfinder

Wayfind a foggy, multi-session effort into an accepted repository spec and separate implementation-ticket drafts. Use when the destination is known but important decisions, dependencies, or scope are not yet clear enough to implement safely.

★ 152
PromptPartner
PromptPartner/agentsmith

verify

Answer "is this shippable / done?" with evidence before a commit or PR — fires on "verify", "is this done", "ready to ship?", pre-commit or pre-PR. Part of the Agentsmith harness; runs the project's verify phases and never claims "passing" without showing the output (R5).

★ 152
PromptPartner
PromptPartner/agentsmith

new-research

Start a durable research / source note that captures what you read and found — fires on "start a research note", "capture these sources", "log my research". Part of the Agentsmith harness; scaffolds docs/research/<slug>.md so findings live in the repo, never in disposable memory (R9), and are never silently deleted.

★ 152