release-workflow

Name: release-workflow
Author: samilozturk

29stars0forks

How to install release-workflow?

samilozturk/agentlint/release-workflow

$npx -y skills add samilozturk/agentlint --skill release-workflow

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Skill: Release Workflow
2
3	## When to Use
4
5	Use this skill when:
6	- preparing a release-affecting change
7	- checking whether a changeset is required
8	- reviewing `release/next` flow correctness
9	- validating package tag and publish expectations
10
11	## Purpose
12
13	Apply the repository's documented release workflow consistently across CLI and MCP packages.
14
15	## Scope
16
17	### Included
18	- changesets
19	- `PUBLISH.md` and `CONTRIBUTING.md`
20	- release scripts and package dry-runs
21	- package-scoped tag expectations
22
23	### Excluded
24	- manual publish execution
25	- ad hoc versioning strategy changes
26	- git push, mirror, or pipeline debugging outside routine release flow
27
28	## Inputs
29
30	- `change-summary`
31	- `touched-paths`
32	- `published-surface-impact`
33	- `release-goal`
34
35	## Step-by-step Execution
36
37	1. Read `PUBLISH.md`, `CONTRIBUTING.md`, and impacted package files.
38	2. Determine whether the change affects a published package output.
39	3. If yes, require a changeset; if no, explain why not.
40	4. Verify root checks and package dry-run expectations.
41	5. Confirm the expected GitLab release path and package-scoped tag pattern.
42	6. Return a release checklist tailored to the touched files.
43	7. Hand off Git or pipeline incidents to `git-release-ci-ops`.
44
45	## Output Contract
46
47	Return:
48	- changeset required: yes/no + why
49	- affected package(s)
50	- exact verification commands
51	- release path summary
52	- risks or drift to review
53
54	## Verification Commands
55
56	```bash
57	pnpm run build
58	pnpm run release-status
59	pnpm run typecheck
60	pnpm run lint
61	pnpm run test
62	npm pack --dry-run --workspace packages/cli
63	npm pack --dry-run --workspace packages/mcp
64	```
65
66	## Evidence Format
67
68	- touched package(s)
69	- changeset decision
70	- commands listed
71	- release step summary
72	- any process mismatch
73
74	## Safety / DONTs
75
76	- Do not hand-edit package versions or changelogs generated by the release MR flow.
77	- Do not reintroduce dual publish automation.
78	- Do not treat GitHub as the publish control plane.
79	- Do not skip dry-runs when package metadata or release logic changes.
80
81	## Gotchas
82
83	- Changesets are required for published-output changes under `packages/cli`, `packages/mcp`, `packages/shared`, or `packages/core`.
84	- GitLab creates package-scoped tags like `cli-vX.Y.Z` and `mcp-vX.Y.Z`.
85	- The publish job is intentionally manual on tag pipelines.
86	- Docs and tests must stay aligned when public surface changes.

People who liked this also viewed

6 picks

Type

release-workflow

29stars0forks

View on GitHub

How to install release-workflow?

samilozturk/agentlint/release-workflow

$npx -y skills add samilozturk/agentlint --skill release-workflow

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Skill: Release Workflow
2
3	## When to Use
4
5	Use this skill when:
6	- preparing a release-affecting change
7	- checking whether a changeset is required
8	- reviewing `release/next` flow correctness
9	- validating package tag and publish expectations
10
11	## Purpose
12
13	Apply the repository's documented release workflow consistently across CLI and MCP packages.
14
15	## Scope
16
17	### Included
18	- changesets
19	- `PUBLISH.md` and `CONTRIBUTING.md`
20	- release scripts and package dry-runs
21	- package-scoped tag expectations
22
23	### Excluded
24	- manual publish execution
25	- ad hoc versioning strategy changes
26	- git push, mirror, or pipeline debugging outside routine release flow
27
28	## Inputs
29
30	- `change-summary`
31	- `touched-paths`
32	- `published-surface-impact`
33	- `release-goal`
34
35	## Step-by-step Execution
36
37	1. Read `PUBLISH.md`, `CONTRIBUTING.md`, and impacted package files.
38	2. Determine whether the change affects a published package output.
39	3. If yes, require a changeset; if no, explain why not.
40	4. Verify root checks and package dry-run expectations.
41	5. Confirm the expected GitLab release path and package-scoped tag pattern.
42	6. Return a release checklist tailored to the touched files.
43	7. Hand off Git or pipeline incidents to `git-release-ci-ops`.
44
45	## Output Contract
46
47	Return:
48	- changeset required: yes/no + why
49	- affected package(s)
50	- exact verification commands
51	- release path summary
52	- risks or drift to review
53
54	## Verification Commands
55
56	```bash
57	pnpm run build
58	pnpm run release-status
59	pnpm run typecheck
60	pnpm run lint
61	pnpm run test
62	npm pack --dry-run --workspace packages/cli
63	npm pack --dry-run --workspace packages/mcp
64	```
65
66	## Evidence Format
67
68	- touched package(s)
69	- changeset decision
70	- commands listed
71	- release step summary
72	- any process mismatch
73
74	## Safety / DONTs
75
76	- Do not hand-edit package versions or changelogs generated by the release MR flow.
77	- Do not reintroduce dual publish automation.
78	- Do not treat GitHub as the publish control plane.
79	- Do not skip dry-runs when package metadata or release logic changes.
80
81	## Gotchas
82
83	- Changesets are required for published-output changes under `packages/cli`, `packages/mcp`, `packages/shared`, or `packages/core`.
84	- GitLab creates package-scoped tags like `cli-vX.Y.Z` and `mcp-vX.Y.Z`.
85	- The publish job is intentionally manual on tag pipelines.
86	- Docs and tests must stay aligned when public surface changes.

People who liked this also viewed

6 picks

Type