release-workflow

name	release-workflow
description	Guide routine Agent Lint package releases through the repository's GitLab-controlled flow. Use when preparing a release, deciding whether a changeset is required, validating release readiness, or reviewing release-process drift after code changes. Trigger on "release", "changeset", "release/next", "tag plan", "release readiness".
disable-model-invocation	false
activation-mode	on-request
scope	release-management
input-types	["release-request","release-readiness-check","release-process-review"]
outputs	["release-checklist","verification-plan","process-drift-summary"]
safety-tier	elevated
category	cicd-deployment
version	1

Skill: Release Workflow

When to Use

Use this skill when:

• preparing a release-affecting change
• checking whether a changeset is required
• reviewing release/next flow correctness
• validating package tag and publish expectations

Purpose

Apply the repository's documented release workflow consistently across CLI and MCP packages.

Scope

Included

• changesets
• PUBLISH.md and CONTRIBUTING.md
• release scripts and package dry-runs
• package-scoped tag expectations

Excluded

• manual publish execution
• ad hoc versioning strategy changes
• git push, mirror, or pipeline debugging outside routine release flow

Inputs

• change-summary
• touched-paths
• published-surface-impact
• release-goal

Step-by-step Execution

1. Read PUBLISH.md, CONTRIBUTING.md, and impacted package files.
2. Determine whether the change affects a published package output.
3. If yes, require a changeset; if no, explain why not.
4. Verify root checks and package dry-run expectations.
5. Confirm the expected GitLab release path and package-scoped tag pattern.
6. Return a release checklist tailored to the touched files.
7. Hand off Git or pipeline incidents to git-release-ci-ops.

Output Contract

Return:

• changeset required: yes/no + why
• affected package(s)
• exact verification commands
• release path summary
• risks or drift to review

Verification Commands

pnpm run build
pnpm run release-status
pnpm run typecheck
pnpm run lint
pnpm run test
npm pack --dry-run --workspace packages/cli
npm pack --dry-run --workspace packages/mcp

Evidence Format

• touched package(s)
• changeset decision
• commands listed
• release step summary
• any process mismatch

Safety / DONTs

• Do not hand-edit package versions or changelogs generated by the release MR flow.
• Do not reintroduce dual publish automation.
• Do not treat GitHub as the publish control plane.
• Do not skip dry-runs when package metadata or release logic changes.

Gotchas

• Changesets are required for published-output changes under packages/cli, packages/mcp, packages/shared, or packages/core.
• GitLab creates package-scoped tags like cli-vX.Y.Z and mcp-vX.Y.Z.
• The publish job is intentionally manual on tag pipelines.
• Docs and tests must stay aligned when public surface changes.