원클릭으로 Manus에서 모든 스킬 실행

release

스타2

포크1

업데이트2026년 4월 11일 21:25

Prepares and cuts a ra11y release. Dispatches release-captain with the target version, verifies everything, updates changelog, bumps package.json, tags, and (with user confirmation) pushes. Use only for versioned releases.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

vanctran

vanctran/ra11y

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

/release $ARGUMENTS

Cuts a ra11y release at version $1. disable-model-invocation: true is intentional — only the user should trigger releases, never the model on its own.

Preconditions

On main, up to date with origin.
Working tree clean.
$1 is a valid semver string.
$1 > current package.json.version.
bun run verify && bun run build && bun run bench all green.

Workflow

Preflight: confirm all preconditions.
Dispatch release-captain with $1. It owns the full release workflow:
- Rewrites the CHANGELOG.md Unreleased section into a versioned section.
- Bumps package.json.version.
- Creates the release commit and tag.
- Returns with the tag created but not pushed.
User confirmation: print a summary of what will happen when the tag is pushed (CI → npm publish → GitHub release). Ask the user to confirm before pushing.
On confirmation: git push origin main && git push origin v$1.
Watch CI: print the Actions URL. Poll the release workflow until it finishes.
Verify: npm view @ra11y/core version must equal $1.
GitHub release: gh release create v$1 --notes-file <tmp-changelog-excerpt>.
Open next cycle: add a fresh ## [Unreleased] section at the top of CHANGELOG.md and commit chore(release): open v<next>-dev cycle.
Report the final links and version.

Safety

Tag push is irreversible. Always confirm with the user before step 4.
Never publish from a laptop. CI has provenance configured; local publishes don't.
Never force-push anything. If something goes wrong, cut a patch release.
Never skip bench. A release = measured + green.
2FA must be active on the npm account publishing the release.

Return format

version: v$1
previous: v<x>
bump: major | minor | patch
verify: passed
bench: inside budget
commits: [release commit sha]
tag: v$1
tag_pushed: yes (user confirmed)
ci_status: <link>
npm_status: <link>
github_release: <link>
next_cycle_commit: <sha>

이 저장소의 다른 Skills

같은 저장소

continue

vanctran/ra11y

Parallel-track dispatcher. Reads .claude/backlog.md, picks the next unchecked item from each of up to 3 active tracks, dispatches them in parallel to specialist subagents, verifies, commits, and checks off. The primary entry point for autonomous ra11y development.

2026-05-052

add-standard

vanctran/ra11y

Scaffolds a new accessibility standard module (metadata, criteria, standard export, tests, kb entry). Delegates the criteria enumeration to spec-researcher + standard-builder. Use when adding any conformance framework.

2026-04-202

add-rule

vanctran/ra11y

Scaffolds a new ra11y rule end-to-end from a criterion ID using the evaluator-optimizer pattern — spec-researcher produces WCAG context, rule-implementer generates, a11y-reviewer critiques, iterate up to 3 times, then code-reviewer signs off. Use when adding any new rule.

2026-04-172

verify

vanctran/ra11y

Universal preflight — runs the full check sequence (typecheck, lint, tests, zero-dep, cycles, network isolation, limits, tsdoc, mermaid, kb drift) through the single `bun run verify` entrypoint. Use before every commit and before handing off to another agent.

2026-04-132

add-formatter

vanctran/ra11y

Scaffolds a new output formatter — file in src/output/formatters/, snapshot tests, CLI --format registration, and a short doc stub. Use when adding terminal/json/sarif/junit/html/markdown/plain or a custom format.

2026-04-112

bench

vanctran/ra11y

Runs scripts/bench.ts against the performance budget and reports the result. Fails if any scenario exceeds budget. Appends a row to docs/performance.md on success.

2026-04-112

name	release
description	Prepares and cuts a ra11y release. Dispatches release-captain with the target version, verifies everything, updates changelog, bumps package.json, tags, and (with user confirmation) pushes. Use only for versioned releases.
argument-hint	<version>
disable-model-invocation	true
allowed-tools	Read Edit Bash(git ) Bash(bun ) Bash(npm ) Bash(gh )

/release $ARGUMENTS

Cuts a ra11y release at version $1. disable-model-invocation: true is intentional — only the user should trigger releases, never the model on its own.

Preconditions

On main, up to date with origin.
Working tree clean.
$1 is a valid semver string.
$1 > current package.json.version.
bun run verify && bun run build && bun run bench all green.

Workflow

Preflight: confirm all preconditions.
Dispatch release-captain with $1. It owns the full release workflow:
- Rewrites the CHANGELOG.md Unreleased section into a versioned section.
- Bumps package.json.version.
- Creates the release commit and tag.
- Returns with the tag created but not pushed.
User confirmation: print a summary of what will happen when the tag is pushed (CI → npm publish → GitHub release). Ask the user to confirm before pushing.
On confirmation: git push origin main && git push origin v$1.
Watch CI: print the Actions URL. Poll the release workflow until it finishes.
Verify: npm view @ra11y/core version must equal $1.
GitHub release: gh release create v$1 --notes-file <tmp-changelog-excerpt>.
Open next cycle: add a fresh ## [Unreleased] section at the top of CHANGELOG.md and commit chore(release): open v<next>-dev cycle.
Report the final links and version.

Safety

Tag push is irreversible. Always confirm with the user before step 4.
Never publish from a laptop. CI has provenance configured; local publishes don't.
Never force-push anything. If something goes wrong, cut a patch release.
Never skip bench. A release = measured + green.
2FA must be active on the npm account publishing the release.

Return format

version: v$1
previous: v<x>
bump: major | minor | patch
verify: passed
bench: inside budget
commits: [release commit sha]
tag: v$1
tag_pushed: yes (user confirmed)
ci_status: <link>
npm_status: <link>
github_release: <link>
next_cycle_commit: <sha>