Skip to content
Skills Library
Management & product · Planning

release

/release

Run a team release: assemble the change list from the diff, write release notes for the audience that reads them, produce the pre-flight and post-deploy checklist with an owner per step, state the rollback path, audit the licenses of the dependencies it ships against the project's own policy, and record who approved the go decision. Use before deploying to staging or production, when cutting a version, when writing notes for a client, or when the licenses of what a release ships need checking. Triggers on: "release", "deploy checklist", "release note", "license audit", "phát hành", "ghi chú ph

Repository
aiteamkit ↗
Licence
MIT
Last repository change
24.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Run a team release: assemble the change list from the diff, write release notes for the audience that reads them, produce the pre-flight and post-deploy checklist with an owner per step, state the rollback path, audit the licenses of the dependencies it ships against the project's own policy, and record who approved the go decision. Use before deploying to staging or production, when cutting a version, when writing notes for a client, or when the licenses of what a release ships need checking. Triggers on: "release", "deploy checklist", "release note", "license audit", "phát hành", "ghi chú ph

Triggers from the description

releasedeploy checklistrelease notelicense auditphát hành

Arguments

/release [version|tag-range] [--notes|--checklist] [--audience internal|client] [--env <name>] [--out <path>]
Original author description

Run a team release: assemble the change list from the diff, write release notes for the audience that reads them, produce the pre-flight and post-deploy checklist with an owner per step, state the rollback path, audit the licenses of the dependencies it ships against the project's own policy, and record who approved the go decision. Use before deploying to staging or production, when cutting a version, when writing notes for a client, or when the licenses of what a release ships need checking. Triggers on: "release", "deploy checklist", "release note", "license audit", "phát hành", "ghi chú ph

How it works

  1. Scope
  2. Roles
  3. Invocation
  4. Workflow
  5. Output
  6. Ticket
  7. Definition of done
Original SKILL.md headings · 159 lines, 1,522 words
SKILL.md preview
---
name: release
description: >
  Run a team release: assemble the change list from the diff, write release notes for the audience
  that reads them, produce the pre-flight and post-deploy checklist with an owner per step, state
  the rollback path, audit the licenses of the dependencies it ships against the project's own
  policy, and record who approved the go decision.
  Use before deploying to staging or production, when cutting a version, when writing notes for a
  client, or when the licenses of what a release ships need checking.
  Triggers on: "release", "deploy checklist", "release note", "license audit", "phát hành",
  "ghi chú phát hành", "kiểm tra license thư viện", "cut a version", "go live", "リリース",
  "リリースノート", "ライセンスチェック", "ship this", "/atk:release".
argument-hint: "[version|tag-range] [--notes|--checklist] [--audience internal|client] [--env <name>] [--out <path>]"
---

# Release Management (`atk:release`)

Turns a set of merged commits into a release a team can execute at a known hour with a known way
back. The rollback path is written before the deploy, not improvised during it.

## Scope

Handles: collecting the change list from git and the tracker, writing release notes per audience,
building the checklist with owners and timings, listing migrations and config changes, the license
audit of the dependencies it ships, stating the rollback path, and recording the go or no-go
decision.

Does NOT handle: executing the deployment, which the pipeline and SRE own; testing (`atk:qa`); or
handling a failed release, which is `atk:incident`.

## Roles

PM owns the go decision and the client communication. SRE owns execution and the rollback. QA signs
off the test result. Tech Lead signs off the technical risk. See `shared/team-roles.md`.

## Invocation

```bash
/atk:release <version>                # Full release artifact for a version
/atk:release v1.3.0..HEAD             # Build from an explicit tag or commit range
/atk:release --notes --audience client  # Client-facing notes only, no internal detail
/atk:release --checklist --env prod   # Deployment checklist for a named environment
/atk:release --out <path>             # Override the default output path
```

## Workflow

```
[1. Collect changes] -> [2. Notes per audience] -> [3. Risk and migration] -> [4. Checklist] -> [5. Go decision]
```

Before step 1, read `.atk/overrides/release.md` when it exists, per rule 7 of `shared/team-roles.md`.
Then, before anything else, create this run's trace, `<docs root>/derived/traces/release/<run-id>.md`:
read the kit's `shared/run-trace.md` and do what it says before the file, at each step, and at the close.

### 1. Collect the changes

Read the commit range and the linked tickets. Where the shape in `.atk/profile.md` names member
repositories, there is no single range: read one per repository in the Repositories table, say which
repository each change came from, and name any member whose range could not be read rather than
leaving it out of the notes. Group by user-visible feature, fix, and internal
change. A commit with no ticket and no clear user effect is listed under internal and flagged, not
dropped.

### 2. Notes per audience

Internal notes carry ticket IDs, migrations, config keys, and known issues. Client notes carry what
changed for the user, in the client's language, with no internal IDs and no blame for the bugs being
fixed. Never publish internal notes to a client by default.

### 3. Risk and migration

List every schema migration with its duration estimate, its reversibility, and whether it requires
downtime. List every new or changed config key and secret, and where it must be set per environment.
Flag anything that cannot be rolled back, because that changes the go decision.

Where a security record under `docs/records/security/` that is not `SUPERSEDED` covers this range,
link it, and carry each open Critical or High finding into the checklist as a blocking item by its
ID, its severity, and its `Accepted by` cell as the record has it, never by its description. A
release record reaches the client, and an unfixed vulnerability described there is disclosed to
everyone who reads it. An empty `Accepted by` cell is an unchecked item, not an accepted risk.

Run the license audit per `references/license-audit.md`, record the command and whose it was, and
carry its items into the checklist as that file's severity table says, the two most severe levels as
blocking with an empty sign-off.

Read the run records under `docs/records/test-runs/` that are not `SUPERSEDED` across this range, the
way the security records above are read, because a fix usually ships in a later build than the run
that found the defect. A record is in the range when the build it names is a commit or version inside
the range, or, where it names neither, when its `created` date falls after the previous release's
tag; on a first release every record counts. Records sort by the time in their file name,
`YYMMDD-HHMM`, then by a `-2`, `-3` suffix, the unsuffixed file first, which is what "newest", "after" and "later" mean below; `created` holds only a date and
is the fallback for a name that carries no time. Then:

- **Evidence behind QA's sign-off.** For each cases file the range touches, link its newest run record
  whose scope is not `retest`, and, where that one's scope is `ids`, every other run record of the same
  build whose scope is not `retest`, since a run split between testers and `atk:run-cases` is several
  `ids` records that together make the pass; then the retest records after them, with the build tested, the scope, the
  summary, and the record's `status` as the record states them. Where that run tested an earlier build
  than the one being released, say so; where a record is not `APPROVED`, the QA sign-off line stays
  unchecked, naming the approver it waits on. A feature in the range with no run record is listed as
  having none.
- **Blocking defects.** A defect blocks when its severity is one of the two most severe levels in the
  severity table of that feature's test plan, which is the master test plan's where the feature plan
  has none, per Reading a section in `skills/qa/references/test-plan-template.md`, with the master
  plan found per Where the master plan is in the same file, read from what each
  level means rather than from where
  it sits in the table, whatever the plan names them; where the order cannot be told, ask the QA lead.
  A severity of `TBD` blocks too, and the QA lead's classification is recorded in this release
  record's checklist beside the item, since a run record's content cannot change. With neither
  plan, the
  tester's scale decides, and the item says there was none. The defects read are those in the range,
  plus any still blocking in the previous release record, carried forward so a defect found before
  that release and never fixed does not drop out of sight.
  A defect stops blocking once a later record passed its case, whatever that record's scope: a retest,
  a full run, or an `ids` run such as one `atk:run-cases` wrote. A
  `Ticket` of `not raised: not a bug` or `not raised: duplicate of ...` lifts the block only when the
  person named after it is the QA lead, and the item says who. One bug is one item: defects whose `Ticket` names the same
  issue, an original and its failed retests, are grouped, and the newest stands for them; so are the
defects of one case in two runs of the same cases. Each item
  names its defect ID, its case ID, its `Ticket` cell, and the path of its record, since defect IDs
  repeat from one record to the next.
- **What reaches the client.** A defect marked `Security: yes`, or whose `Ticket` starts with
  `private`, is named by its ID only, in the checklist and among the known issues
  alike, never by its description, for the reason given above for security findings; a `Ticket` cell
  of `not raised` or `private` is written without the reason after it, since the reason can describe
  the vulnerability.

With no run record in the range, QA's sign-off has nothing on disk behind it, and the release record
says so rather than leaving the line looking checked.

### 4. Checklist

Three phases, each step with an owner and an expected duration: pre-flight (backup taken, migration
rehearsed on staging, config set, feature flags, maintenance notice, on-call confirmed), deploy
(order across services, health checks), and post-deploy (smoke tests, metrics and error rate to
watch, and for how long).

The rollback section states the trigger condition, the exact steps, the data implication, and who
may call it without waiting for a meeting.

### 5. Go decision

Record each sign-off with a name and a state. An unchecked blocking item means no-go; say so plainly
rather than presenting a release as ready.

## Output

Written to `docs/records/releases/<version>.md` per `shared/artifact-paths.md`. Sections: front matter,
scope and change list, internal notes, client notes, migrations and config, the license audit,
checklist with owners,
rollback plan, sign-offs, and known issues shipping with the release.

Putting it where the team can see it is `atk:git`, which follows the artifact section of
`shared/finalize-steps.md`: the branch, the commit, and the judgement about whether this one belongs
in a pull request for its approver to read. Whether it is committed at all is the persistence group
it falls into, per `shared/artifact-paths.md`.

## Ticket

Follow `shared/ticket-adapters.md`. Map the release to the tracker's release, fix version, or
milestone, and link each included ticket.

## Definition of done

- [ ] Every included change traces to a commit and, where one exists, a ticket.
- [ ] Client notes contain no internal ticket IDs or internal terminology.
- [ ] Every migration states whether it is reversible and whether it needs downtime.
- [ ] Every checklist step has an owner.
- [ ] The rollback trigger, steps, and caller are written before the deploy.
- [ ] The license audit names its policy and command, or says it was not run and why, and every
      item at the two most severe levels is a blocking item with an empty sign-off.
Files in this package (3)
  • SKILL.md 10 KB
  • evals/trigger_evals.json 2 KB
  • references/license-audit.md 5 KB

Versions

RepositoryScoreLicence
This page · lamngockhuong/aiteamkit100MIT
josephfung/curia100MIT
max-sixty/worktrunk100MIT
gtapps/hermitd100MIT
gtapps/hermitd100MIT
anthony-chaudhary/fak100Apache-2.0
tractorjuice/arc-kit100MIT
drvoss/everything-copilot-cli100MIT
sma1lboy/rove100MIT

Database snapshot: 13.11.2026 · package version 6aa857bb203f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90release-checklist
    Prepares a routine release after launch: scope from done stories, CI and test status, migration safety, feature flags, changelog, release notes, deploy and rollback steps, and a go/no-go. Use for every production release after the first launch.
  • 95pm-release
    Use when: 风险管控完成后准备上线发布、需要制定上线检查清单与回滚方案、正式发版流程 Do NOT use when: 上线流程已标准化且由运维自动化执行、仅需简单发布无需检查清单
  • 98release-manager
    Guided run-book for cutting a DevThrottle release - assemble the changes, write the release notes, coordinate the internal docs site, cut the tag, and announce it. Triggers on "/release-manager", "cut a release", "prepare a release", "ship a release", "do the release".
  • 100release-checklist
    Build a release checklist and go/no-go plan covering semantic versioning, changelog, green CI and security gates, signed artifacts, database migrations, feature flags, staged rollout and a tested rollback plan. Use when the user is preparing a release or deploy, cutting a tag,…
  • 100hatch3r-release
    Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.
  • 86release-notes
    Compare the repository with the team's Folio wiki and write release notes: read git log since the last tag, read the Roadmap table, create or update a Release notes page and add what the roadmap table is missing. Use when asked for release notes or to sync the wiki with the code.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.