/release-pastiche
Ship a pastiche release — version bump, plugin build, CHANGELOG entry, release commit, tag, GitHub Release, milestone close. Use when the user invokes `/release-pastiche` after a TODO group's final feat→main merge. Human-triggered only; never run from an automated routine.
Claude Code
$ npx -y skills add retz8/pastiche --skill release-pastiche --agent claude-code
Codex
$ npx skills add retz8/pastiche --skill release-pastiche -a codex -y
Cursor
$ npx skills add retz8/pastiche --skill release-pastiche -a cursor -y
Gemini CLI
$ npx skills add retz8/pastiche --skill release-pastiche -a gemini-cli -y
GitHub Copilot
$ npx skills add retz8/pastiche --skill release-pastiche -a github-copilot -y
OpenCode
$ npx skills add retz8/pastiche --skill release-pastiche -a opencode -y
Windsurf
$ npx skills add retz8/pastiche --skill release-pastiche -a windsurf -y
SKILL.md
release-pastiche.SKILL.mdname: release-pastiche
description: Ship a pastiche release — version bump, plugin build, CHANGELOG entry, release commit, tag, GitHub Release, milestone close. Use when the user invokes `/release-pastiche` after a TODO group's final feat→main merge. Human-triggered only; never run from an automated routine.
release-pastiche
Run on `main`, clean working tree, after every task of the group has merged.
Workflow
1. **Determine the version.** Default: the completed group's minor from `_dev/TODO.md` (provisional — confirm with the user; hotfix releases are a patch bump instead). 2. **Bump** `version` in `package.json`. 3. **Build:** `npm run build` — verify `dist/claude-code/` regenerated and its `plugin.json` carries the new version. 4. **CHANGELOG entry.** Move `[Unreleased]` content (if any) and derive the rest from commits since the last release tag: `feat(...)` → *Added*, `fix(...)` → *Fixed*, breaking/behavior changes → *Changed*. Section header: `## [<version>] - <today>`. Fresh empty `[Unreleased]` on top. 5. **Commit** everything as one commit: `chore(release): v<version>`. 6. **Tag** `v<version>` and push branch + tag. 7. **GitHub Release:** `gh release create v<version>` with the new CHANGELOG section as body. 8. **Close the milestone** for the shipped group. 9. **Tick TODO.md**: confirm all the group's task checkboxes are ticked and parent issues closed; flag any that aren't.
Read more
name: release-pastiche description: Ship a pastiche release — version bump, plugin build, CHANGELOG entry, release commit, tag, GitHub Release, milestone close. Use when the user invokes `/release-pastiche` after a TODO group's final feat→main merge. Human-triggered only; never run from an automated routine.
release-pastiche
Run on `main`, clean working tree, after every task of the group has merged.
Workflow
1. **Determine the version.** Default: the completed group's minor from `_dev/TODO.md` (provisional — confirm with the user; hotfix releases are a patch bump instead). 2. **Bump** `version` in `package.json`. 3. **Build:** `npm run build` — verify `dist/claude-code/` regenerated and its `plugin.json` carries the new version. 4. **CHANGELOG entry.** Move `[Unreleased]` content (if any) and derive the rest from commits since the last release tag: `feat(...)` → *Added*, `fix(...)` → *Fixed*, breaking/behavior changes → *Changed*. Section header: `## [<version>] - <today>`. Fresh empty `[Unreleased]` on top. 5. **Commit** everything as one commit: `chore(release): v<version>`. 6. **Tag** `v<version>` and push branch + tag. 7. **GitHub Release:** `gh release create v<version>` with the new CHANGELOG section as body. 8. **Close the milestone** for the shipped group. 9. **Tick TODO.md**: confirm all the group's task checkboxes are ticked and parent issues closed; flag any that aren't.
Pastiche is a Claude Code plugin for Frontend UI implementation. Given a frontend task, it produces code that follows your established design system and component library — not by inventing, but by faithfully executing within the vocabulary your team already
Other skills on pastiche.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about release-pastiche.
- Which coding agents can use release-pastiche?
- release-pastiche installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

