Menu
Bump package versions and update CHANGELOG.md so consumers can see what happens between releases. Use when a feature or fix branch is ready.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | bump |
| description | Bump package versions and update CHANGELOG.md so consumers can see what happens between releases. Use when a feature or fix branch is ready. |
CHANGELOG.md at the monorepo root tells package consumers what changed. Every branch that changes a published package (styles, react, icons) must bump the affected versions and document the changes before being merged.
git diff origin/main...HEAD --stat and git log origin/main..HEAD show which packages changed. Ignore packages with no consumer-facing change.0.0.x + 1) in each affected <package>/package.json. The repository convention is one bump per feature branch, folded into the feature commit.react consuming new styles CSS classes), update the corresponding peerDependencies range (e.g. "@ippon-ui/styles": "~0.0.7").mise setup so the lockfile stays consistent.CHANGELOG.md: add a release entry right after the introduction, above the previous entries.mise build, mise lint-ci and mise test-unit-ci must pass.## YYYY-MM-DD — @ippon-ui/styles X.Y.Z · @ippon-ui/react X.Y.Z
### Added
- `component` organism: what it brings to the consumer.
### Changed
- What changed and what it means for the consumer.
·.Added, Changed, Deprecated, Removed, Fixed, Security. Only include the categories that apply.Pattern Libreary which allows representing graphical components. Provides CSS and uses HTML as a template language. This is where tokens, quarks, atoms, molecules, organisms, templates are defined.
Use when the user wants to pick a GitHub issue to work on from a list. Lists open issues (the ones already assigned to the current user first), lets the user choose one, self-assigns it, creates an isolated workspace, runs setup, clarifies the issue one question at a time, plans (one approval checkpoint), implements, opens a draft PR, and folds every later change — including review feedback — into a single amended commit.
Use when the user wants to clean up stale or merged git worktrees under ~/.workspace (e.g. after PRs are merged and their remote branches deleted). Prunes workspaces whose remote branch is gone. Companion to pick-issue-to-pr.
Component Library with React components used by the application.