Skill
divide-task
Divide a specced pastiche task into sub-task GitHub issues with autonomy and dependency labels, mirror them into `_dev/TODO.md`, and update the parent issue.…
Development
Skill
/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.
Install
$ npx -y skills add retz8/pastiche --skill release-pastiche --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/release-pastiche
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
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.
Ships withpastiche
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
Get the whole plugin
Stats
4
Stars
0
Forks
Maintained
Maintenance
TypeScript
Language
MIT
License
3mo ago
Last commit
4mo ago
Created
Repo: retz8/pastiche
Other skills on pastiche.
Skill
grill-to-spec
Convert a completed grill-me session into a spec file. Captures only the task and the decisions locked during grilling — no implementation details, no invented…
Skill
pick-up-task
Pick up or resume a task from `_dev/TODO.md` — marks `[WIP]`, creates or switches to the task's feature branch, rebases with main. Use when the user invokes…
Skill
rebase-feat-with-main
Rebase the current pastiche feature branch onto main to absorb hotfixes. Use when the user invokes `/rebase-feat-with-main`, when resuming a task, or after a…
Skill
pastiche-init
Use when bootstrapping pastiche in a frontend repo for the first time — scaffolds `pastiche/{config.yaml, FACT.md, KNOWLEDGE.md, WISDOM.md}` and extracts FACT.…
Skill
pastiche-lint
Use to re-validate `pastiche/{config.yaml, FACT.md, KNOWLEDGE.md, WISDOM.md}` after hand-editing any of them outside the mutator skills. Thin manual wrapper…