Release pastiche
drawing UI consistently with agents, at the top of Design System + Component Library
npx -y skills add retz8/pastiche --skill release-pasticheAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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
1.4 KB, as published. Nobody here has run it
release-pastiche
Run on main, clean working tree, after every task of the group has merged.
Workflow
- 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). - Bump
versioninpackage.json. - Build:
npm run build— verifydist/claude-code/regenerated and itsplugin.jsoncarries the new version. - 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. - Commit everything as one commit:
chore(release): v<version>. - Tag
v<version>and push branch + tag. - GitHub Release:
gh release create v<version>with the new CHANGELOG section as body. - Close the milestone for the shipped group.
- Tick TODO.md: confirm all the group's task checkboxes are ticked and parent issues closed; flag any that aren't.