메뉴
Perform a project release: bump the semver `version` in package.json, summarize changes since the last release, and hand off to the health-checkup. Use when cutting a release, bumping the project version, or asked to "version up".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | version-up |
| description | Perform a project release: bump the semver `version` in package.json, summarize changes since the last release, and hand off to the health-checkup. Use when cutting a release, bumping the project version, or asked to "version up". |
The release ritual for syakoo-lab itself: bump this project's own version in package.json
and run the design checkup that must accompany it.
This is the project's own release, not a dependency update. (Dependency-update PRs are a separate, Renovate-automated concern and are out of scope here.)
package.json version).Not for dependency bumps or feature work.
Run as a dedicated PR, separate from feature work (consistent with continuous-improvement).
version in package.json and locate the previous
bump (git log --oneline -- package.json or the latest release tag).version in package.json only.git log. Group by
the kind of change (features, fixes, internal) so it doubles as release notes.health-checkup. Run that skill over everything changed since the last release
(design-drift audit + deepen-modules pass). The version bump is its trigger.create-pull-request, including the change summary.health-checkup
(design debt compounds).health-checkup; this skill only triggers it.Periodic code health checkup for design drift not caught by CI. Use at version bumps or when asked for a code health check / 健康診断 / 健診. Audits logged advisory deviations and runs a deepen-modules pass.
Project coding conventions and architecture constraints. Use when implementing, creating, or modifying components and modules (e.g. "create a component", "implement this feature").
Create a PR aligned with the AI-led workflow: summary, design (when relevant), impact and risks. Use when creating a pull request, opening a PR, pushing for review, or completing implementation of an issue.
Triage GitHub PR review feedback (top-level, inline, threads); implement agreed items; escalate disagreements or questions. Includes lint/test checks, per-thread replies with commit SHA, and a chat summary. Use when fixing review feedback on an open PR—not for greenfield implementation only.
Propose codifying reusable lessons from trial-and-error or explicit user requests into lint, rules, or skills. Use near task completion after failed first attempts, or when the user asks to "make it a rule" or "leave a lesson". NOT for empirically testing instructions on fresh agents (tune-prompt) or drafting a new skill without a lesson to codify.
Empirically test skills, rules, or prompts on fresh agents with scored checklists; edit one theme per cycle until instructions land. Use after creating or heavily revising agent instructions, when agents misbehave on those instructions, or when validating that a skill is followed correctly. NOT for codifying runtime lessons after task failures (suggest-improvement) or drafting a new skill without empirical validation.