Run any Skill in Manus with one click

final-release-review

Stars23

Forks20

UpdatedMarch 17, 2026 at 02:29

Compare the current Qubex release candidate against the previous tag and review release readiness. Use before beta, rc, or GA cuts to check version drift, release notes, compatibility messaging, build health, and validation status; use the bundled script to resolve the comparison range and collect the release diff mechanically.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

amachino

amachino/qubex

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	final-release-review
description	Compare the current Qubex release candidate against the previous tag and review release readiness. Use before beta, rc, or GA cuts to check version drift, release notes, compatibility messaging, build health, and validation status; use the bundled script to resolve the comparison range and collect the release diff mechanically.

Final Release Review

Overview

Review the release candidate from repository state, version files, docs, and the previous tag. Produce blockers, risks, and missing release tasks while letting the script resolve the comparison range and diff summary.

Workflow

Resolve candidate context.
- Read VERSION, pyproject.toml, and release-note files under docs/release-notes/.
- Identify the intended release version from the working tree or target tag.
Select comparison tags.
- Prefer the bundled script: uv run python .agents/skills/final-release-review/scripts/collect_release_diff.py
- Compare against the immediate predecessor tag first.
- If the candidate starts a new stable line, also compare against the latest stable predecessor.
Gather the diff summary.
- Use the script output for the base tag, compare range, git log, and git diff --stat summary.
- Note doc, test, and packaging deltas separately.
Check release gates.
- make check-release-version
- make check
- For release packaging work, make build-all
- For docs-heavy release work, uv run mkdocs build
Check release artifacts.
- Release notes and migration guides reflect the actual code.
- Version strings are synchronized.
- Compatibility claims match released behavior.
- Known limitations and non-blockers are documented.
Report readiness.
- Separate blockers, risks, and nice-to-have follow-ups.
- Call out missing release-note entries, version drift, failing checks, and undocumented breaking behavior.

Bundled script

`scripts/collect_release_diff.py`

Use this script for deterministic release-review mechanics:

resolve the previous release tag automatically
print the compare range
collect git log --oneline and git diff --stat

Keep model work focused on interpreting compatibility risk, migration needs, and release readiness.

More from this repository

same repository

code-change-verification

amachino/qubex

Run the mandatory Qubex verification stack when changes affect runtime code, tests, examples, packaging, or build/test behavior. Use after substantive code changes, and do not mark the work complete until the required checks pass in the `uv` environment.

2026-03-1823

docs-sync

amachino/qubex

Audit Qubex documentation against code changes and report missing, incorrect, or outdated docs. Use when public APIs, behavior, setup, dependencies, examples, release notes, or developer guidance change; by default, inspect and prioritize the required updates first, then edit only after the user asks for docs changes.

2026-03-1823

examples-auto-run

amachino/qubex

Run Qubex examples in non-interactive auto mode, capture logs, and provide exact rerun commands. Use when validating notebooks or tutorial examples after code, docs, or dependency changes, especially for simulator and other offline examples; use the bundled script for execution, logging, and rerun-file generation instead of rebuilding the shell recipe by hand.

2026-03-1723

implementation-strategy

amachino/qubex

Choose the Qubex compatibility boundary and implementation approach before editing runtime code, public APIs, imports, config formats, or behavior. Use before making API or runtime changes, especially when you must decide between direct cleanup and backward-compatibility handling.

2026-03-1723

openai-knowledge

amachino/qubex

Pull current OpenAI API and platform documentation through the official docs workflow. Use when a task depends on current OpenAI models, APIs, SDKs, or platform behavior and memory could be stale.

2026-03-1723

pr-draft-summary

amachino/qubex

Create a branch suggestion, PR title, and draft description after substantive Qubex changes are finished. Trigger when wrapping up a moderate-or-larger change that touched runtime code, tests, build config, or docs with behavior impact and you need a PR-ready handoff block with summary, compatibility notes, and verification results.

2026-03-1723

name	final-release-review
description	Compare the current Qubex release candidate against the previous tag and review release readiness. Use before beta, rc, or GA cuts to check version drift, release notes, compatibility messaging, build health, and validation status; use the bundled script to resolve the comparison range and collect the release diff mechanically.

Final Release Review

Overview

Workflow

Resolve candidate context.
- Read VERSION, pyproject.toml, and release-note files under docs/release-notes/.
- Identify the intended release version from the working tree or target tag.
Select comparison tags.
- Prefer the bundled script: uv run python .agents/skills/final-release-review/scripts/collect_release_diff.py
- Compare against the immediate predecessor tag first.
- If the candidate starts a new stable line, also compare against the latest stable predecessor.
Gather the diff summary.
- Use the script output for the base tag, compare range, git log, and git diff --stat summary.
- Note doc, test, and packaging deltas separately.
Check release gates.
- make check-release-version
- make check
- For release packaging work, make build-all
- For docs-heavy release work, uv run mkdocs build
Check release artifacts.
- Release notes and migration guides reflect the actual code.
- Version strings are synchronized.
- Compatibility claims match released behavior.
- Known limitations and non-blockers are documented.
Report readiness.
- Separate blockers, risks, and nice-to-have follow-ups.
- Call out missing release-note entries, version drift, failing checks, and undocumented breaking behavior.

Bundled script

`scripts/collect_release_diff.py`

Use this script for deterministic release-review mechanics:

resolve the previous release tag automatically
print the compare range
collect git log --oneline and git diff --stat

Keep model work focused on interpreting compatibility risk, migration needs, and release readiness.