메뉴
Use when starting Step 1 of legacy refactoring protocol — runs a 2-4 hour feasibility spike for one Bounded Context. Triggers on '/legacy-spike <module>' or when user asks for a feasibility check, BC scope decision, or 'чи злітає переписування цього модуля'.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Prepare and verify the repository files required to deploy this Next.js project to one Ubuntu VPS with Docker Compose and a GitHub self-hosted runner. Use when creating or reviewing Dockerfile.production, compose.vps.yml, the health route, persistent SQLite storage, or deploy-vps.yml before a VPS release.
Decide and apply the next semver for a release. Triggers on "bump the version", "what version is next", "/bump-version", "простав версію", "яка наступна версія". Reads the next number from the deterministic scripts/next-version.sh (NEVER guesses it), explains in plain language WHICH part moved and why (e.g. "MINOR, because a feat landed: filter notes by tag"), edits the version line in pyproject.toml, and proposes the matching `git tag vX.Y.Z`. The number is decided by a rule; the agent explains and applies — the human confirms the tag. Never pushes a tag itself.
Find and fix where docs/api.md fell behind the code. Triggers on "check for doc drift", "is the API doc up to date", "/check-docs-drift", "перевір дрейф документації", "docs drift". Runs the deterministic scripts/check-docs-drift.py (parses the public NoteBook methods with ast, compares to what docs/api.md documents — NO LLM finds the gap), reports the drift, and PROPOSES the doc edit that closes it. The gap is found by parsing; the agent writes the missing documentation in the doc's existing style. Edits only docs/; never commits or pushes.
Turn a repeated mistake into a durable, path-scoped rule in .claude/rules/. Triggers on "codify this rule", "make a rule so this doesn't happen again", "/codify-rule", "закодифікуй правило", "петля помилка-правило". Use only when the same mistake showed up TWICE (twice = a pattern, once = noise). Names the wrong shape and the right shape with one short example of each, scopes the rule to the paths that matter, and leaves the edit in the working tree so the next agent on this repo inherits the fix. Edits only .claude/rules/; never commits or pushes.
Curate the [Unreleased] section of docs/CHANGELOG.md from git history. Triggers on "curate the changelog", "update the changelog", "/curate-changelog", "онови changelog", "курування журналу". Reads git log since the last tag, FILTERS out what a reader never feels (test/ci/chore/merge), GROUPS commits about one feature into one bullet, and REWRITES technical subjects into plain language under the six Keep a Changelog categories (Added/Changed/Deprecated/ Removed/Fixed/Security). The result must have FEWER lines than the raw log — that is the proof of curation, not a dump. Leaves the edit in the working tree; never commits or pushes.
Draft partner-facing release notes from the same commits as the changelog. Triggers on "draft release notes", "release notes for the next version", "/release-notes", "нотатки релізу", "release notes партнеру". Same input as curate-changelog, different audience and tone: a short, benefit-first narrative for a user or partner — "what's new for you" — not a categorized engineer's list. Keeps only changes a user actually notices; drops internal refactors and tooling. Prints the notes to the chat to seed a GitHub Release description or a partner announcement. Writes no file.
| name | legacy-spike |
| description | Use when starting Step 1 of legacy refactoring protocol — runs a 2-4 hour feasibility spike for one Bounded Context. Triggers on '/legacy-spike <module>' or when user asks for a feasibility check, BC scope decision, or 'чи злітає переписування цього модуля'. |
| argument-hint | <module-name> (e.g. account, orders, billing) |
| allowed-tools | Read, Grep, Glob, Bash |
| disable-model-invocation | false |
Запускає 2-4-годинну розвідку перед основною роботою. Перевіряє чотири критерії: churn, debt, isolation, feasibility.
<module-name> (обовʼязково) — імʼя нового модуля у internal/. Має бути нейтральним (наприклад account, не users-v2).git log за останні 3 місяці у legacy-папкахfind + wc -l)grep -r "from internal.<old>")grep -E "^def [a-z]")# SPIKE — <module-name>
## 1. Churn (3 місяці)
| File | commits | last touched |
| --- | --- | --- |
| ... | ... | ... |
## 2. Debt indicators
- LOC у legacy: <число>
- # public functions: <число>
- Тестове покриття: <%, через grep на pytest файли>
- TODO/FIXME у модулі: <число>
## 3. Isolation
- Імпортується ззовні: <список модулів які тягнуть legacy>
- Глобальні змінні / singletons: <список>
- Прихована логіка (магічні числа, хардкоди): <короткий список>
## 4. Feasibility verdict
- **Climbs in 1-2 weeks?** YES / NO / RISKY
- Якщо NO/RISKY — який зв'язок заважає, як його розплутати окремим циклом
- Якщо YES — rough Bounded Context boundaries (public interface)
## Rough plan
1. Step 2 — extract <N> файлів через subagents
2. Step 3 — <X> use cases для test plan
3. Step 4 — <Y> chunks (1 use case = 1 коміт за замовчуванням)
## Гіпотези для Step 2 critic
- ...
name(args) → result/legacy-spike account
→ створює SPIKE.md у корені проекту з висновком чи можна переписати users-модуль на account за 1-2 тижні.
users-v2 у rough plan — нейтральне доменне імʼя у <module-name>, інакше тягнеш лабораторні артефакти у прод-код.