From harness-flow
Orchestrates an engineer-level release by aggregating workflow-closeout features, drafting a scope ADR, running fresh regression, syncing changelogs, and producing a tag-ready release pack.
How this command is triggered — by the user, by Claude, or both
Slash command
/harness-flow:releaseThe summary Claude sees in its command listing — used to decide when to auto-load this command
Direct invoke `skills/hf-release/SKILL.md`. **Do not** route through `using-hf-workflow` -> `hf-workflow-router` first — `hf-release` is a standalone skill (ADR-004 D3) that reads disk artifacts directly to drive release-tier work. Steps: 1. Load `skills/hf-release/SKILL.md`. 2. Treat the user request following this command as version hint and scope intent (e.g. `/release v1.2.0` -> version hint `v1.2.0`; `/release` alone -> infer from candidates + SemVer rules in §4). 3. Follow the SKILL.md `Workflow` §1 -> §11 in order: - §1 Entry vs Recovery (read `features/release-vX.Y.Z/release-pa...
Direct invoke skills/hf-release/SKILL.md. Do not route through using-hf-workflow -> hf-workflow-router first — hf-release is a standalone skill (ADR-004 D3) that reads disk artifacts directly to drive release-tier work.
Steps:
skills/hf-release/SKILL.md./release v1.2.0 -> version hint v1.2.0; /release alone -> infer from candidates + SemVer rules in §4).Workflow §1 -> §11 in order:
features/release-vX.Y.Z/release-pack.md to decide new vs continue).workflow-closeout features qualify).docs/decisions/ADR-NNN-release-scope-vX.Y.Z.md).hf-regression-gate skill).features/release-vX.Y.Z/release-pack.md.Hard rules (do not bypass):
hf-release does not enter the hf-workflow-router transition map and does not hand work back to the router. Next Action is null / specific blocker / hf-release §<step> only.git tag, git push --tags, GitHub Release) are project-maintainer actions.task-closeout / blocked features are rejected at §2.Out of scope (explicitly): feature flag lifecycle, staged rollout (0% -> 5% -> 100%), monitoring dashboards, error reporting, SLO config, health checks, CDN / DNS / SSL, rate limiting, post-launch observation windows.
The user request following this command is optional version hint + scope intent (e.g. /release v1.2.0 minor with onboarding + rate-limit, defer billing-export). The skill uses on-disk closeout records to validate the proposed scope.
See docs/decisions/ADR-004-hf-release-skill.md for the full v0.4.0 introduction decision and the rationale for the decoupling stance.
npx claudepluginhub hujianbest/harness-flow --plugin harness-flow/releaseExecutes the Hypo-Workflow release skill, loading instructions from a skill file and running release semantics with user-provided arguments.
/releaseReleases the project using adaptive learned configuration — discovers the release pipeline on first run and caches it. Also supports version bump types and --dry-run preview.
/hatch3r-releaseOrchestrates a release branch cut with SemVer bump, changelog sync, CycloneDX SBOM build, quality gates, and verification — stops before publish for human approval.
/releasePrepares Python project release: validates prereqs/tests/Work Items, updates version in pyproject.toml/src/manifest, generates CHANGELOG, creates git commit/tag, and CI/CD handoff doc. [--dry-run]
/releaseAutomates semantic version releases: analyzes CHANGELOG changes, suggests bump type per conventions, updates version files, creates annotated git tag after confirmation.
/releaseCreates full release: verifies CI/CD, generates changelog, creates GitHub release with v<semver> tag, publishes packages, updates docs, notifies stakeholders.