[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YBQTSA3JS3XEJQJ9XZWJ1":3,"skill-same:01M72YBQTSA3JS3XEJQJ9XZWJ1":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M72YBQTSA3JS3XEJQJ9XZWJ1","fix-term",null,"Use to capture or update domain terms in CONTEXT.md before their meaning drifts — whenever a fuzzy word shows up in an interview, PRD, or review and you want one canonical definition plus a NOT-reference so a homonym can't bite you in six months. Triggers on \"add term {X}\", \"what is {X} in our domain\", \"add to CONTEXT\", \"fix the glossary\", \"define {X}\", \"\u002Fsdlc:fix-term {term}\", \"fix term {X}\", \"додай термін\", \"онови глосарій\", \"що означає {X}\". Lazy-bootstraps docs\u002Ffeatures\u002F{slug}\u002FCONTEXT.md (or repo-root CONTEXT.md; multi-context repos also get CONTEXT-MAP.md updated) from a template, checks for a conflicting existing entry, asks for a one-sentence definition + the concept it's confused with, and appends one line to ## Glossary. Skip generic tech words (HTTP, queue, cache) — those are not domain terms. Output: created\u002Fedited CONTEXT.md (+ CONTEXT-MAP.md updated when multi-context). Runs anytime, no input gate; write-prd and architecture-design read its ## Glossary as the canonical source of role and domain-term names.","genkovich\u002Fagentic-engineering-course-public","genkovich","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14920737?v=4","01M72Y5BWEEZ8VT4DFW6AGGE8X","Kirill Sulimovsky","01M72Y5BXYRGV5PKCVCHEX81WY",15,"MIT","https:\u002F\u002Fgithub.com\u002Fgenkovich\u002Fagentic-engineering-course-public\u002Fblob\u002Fmain\u002Fmodules\u002F6-sdlc\u002Fsdlc\u002Fplugin\u002Fskills\u002Ffix-term\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: fix-term\ndescription: >-\n  Use to capture or update domain terms in CONTEXT.md before their meaning\n  drifts — whenever a fuzzy word shows up in an interview, PRD, or review and\n  you want one canonical definition plus a NOT-reference so a homonym can't\n  bite you in six months.\n  Triggers on \"add term {X}\", \"what is {X} in our domain\", \"add to CONTEXT\",\n  \"fix the glossary\", \"define {X}\", \"\u002Fsdlc:fix-term {term}\", \"fix term {X}\",\n  \"додай термін\", \"онови глосарій\", \"що означає {X}\".\n  Lazy-bootstraps docs\u002Ffeatures\u002F{slug}\u002FCONTEXT.md (or repo-root CONTEXT.md;\n  multi-context repos also get CONTEXT-MAP.md updated) from a template, checks\n  for a conflicting existing entry, asks for a one-sentence definition + the\n  concept it's confused with, and appends one line to ## Glossary. Skip generic\n  tech words (HTTP, queue, cache) — those are not domain terms.\n  Output: created\u002Fedited CONTEXT.md (+ CONTEXT-MAP.md updated when multi-context).\n  Runs anytime, no input gate; write-prd and architecture-design read its\n  ## Glossary as the canonical source of role and domain-term names.\ntriggers:\n  - \u002Fsdlc:fix-term\n  - \"fix term\"\n  - \"add term\"\n  - \"what is X in our domain\"\n  - \"add to CONTEXT\"\n  - \"fix the glossary\"\n  - \"define X\"\n  - \"додай термін\"\n  - \"онови глосарій\"\n---\n\n# Skill: fix-term\n\nLazy utility that fixes the meaning of a domain term in `CONTEXT.md` the moment it first surfaces, so its sense doesn't drift across the pipeline. For each term it captures a one-sentence canonical definition and — when the word is ambiguous — a **NOT-reference** naming the concept it's confused with. Runs anytime, with no upstream gate: a single term mid-interview, or a batch handed over by `write-prd`. The output feeds `write-prd` (role + domain-term names) and `architecture-design` (invariants), which treat `## Glossary` as canonical and override anything that contradicts it.\n\nThis is a capture utility, not a Socratic stage — it does **not** run the shared Socratic loop or critic. The one shared dependency is question phrasing:\n→ [`..\u002F_shared\u002Fask-style.md`](..\u002F_shared\u002Fask-style.md)\n\n## Owner\n\nWhoever drives the conversation — anyone who spots ambiguity. Tech Lead approves the canonical form when a term is contested.\n\n## Inputs\n\n- `\u003Cterm>` — the domain word\u002Fphrase to fix. If not given, ask for it.\n- (Optional) `\u003Cslug>` — feature slug; targets `docs\u002Ffeatures\u002F\u003Cslug>\u002FCONTEXT.md`. Absent → single-context check below.\n- (Optional) `\u003Ccontext>` — bounded-context name (for multi-context repos); detected via `CONTEXT-MAP.md`.\n- (Optional) `pending_glossary_terms` — a batch handed over by `write-prd` after it writes the PRD. Process each term in turn.\n- (Optional) proposed phrasings already surfaced in an interview\u002Fbrainstorm — offer them as definition options instead of asking blank.\n\n## Protocol\n\n1. **Detect context mode.** `test -f CONTEXT-MAP.md` at the repo root.\n   - **Multi-context** (file exists and contains real rows): ask which bounded context `\u003Cterm>` belongs to: «Available contexts: `\u003Clist from CONTEXT-MAP.md>`.» (phrasing per [`..\u002F_shared\u002Fask-style.md`](..\u002F_shared\u002Fask-style.md)). Target `\u003Cctx>\u002FCONTEXT.md`. If the context isn't yet registered in CONTEXT-MAP.md, add a row now (`| \u003Cctx> | \u003Cpath> | \u003C1-line scope> |`).\n   - **Single-context** (no CONTEXT-MAP.md or only a stub): if `\u003Cslug>` is given → `docs\u002Ffeatures\u002F\u003Cslug>\u002FCONTEXT.md`; otherwise → repo-root `CONTEXT.md`. One glossary per file; don't split a term across both.\n2. **Generic-term filter.** Reject words that name infrastructure or transport rather than the business domain (e.g. HTTP, queue, cache, the datastore, a framework, JSON, REST, gRPC). Refuse: «`\u003Cterm>` is technical, not a domain word — its choice belongs in the SAD or an ADR, not the glossary». Continue only for genuine domain vocabulary.\n3. **Bootstrap (lazy).** `test -f \u003Ctarget>`. Missing → copy [`.\u002Ftemplates\u002FCONTEXT.md`](.\u002Ftemplates\u002FCONTEXT.md) to `\u003Ctarget>`. Present → read it.\n4. **Conflict check.** `grep -i \"^- \u003Cterm>\" \u003Ctarget>`.\n   - Found, identical sense → STOP, report «already in the glossary».\n   - Found, different sense → escalate via `AskUserQuestion` (phrasing per [`..\u002F_shared\u002Fask-style.md`](..\u002F_shared\u002Fask-style.md)): «`\u003Cterm>` is already defined as `\u003Cexisting>` — same concept or a different one?». If different, propose a disambiguating pair of names (e.g. a billing-scoped vs a runtime-scoped variant) and fix both.\n   - Not found → continue.\n5. **Ask the canonical definition** — one `AskUserQuestion`: «Define `\u003Cterm>` in this domain, in one sentence». Offer interview\u002Fbrainstorm phrasings as options when available; otherwise free text. Follow the explanatory style in [`..\u002F_shared\u002Fask-style.md`](..\u002F_shared\u002Fask-style.md) — gloss every technical term inline, explain why the definition matters.\n6. **Ask the NOT-reference** — one `AskUserQuestion`: «Which concept does `\u003Cterm>` get confused with, so a future reader doesn't mix them up?». No plausible homonym → `None`.\n7. **Compose one line.** `- \u003Cterm> — \u003Cone-sentence definition>. NOT \u003Cconfused concept + how it differs>.` — or, when step 6 = None, `- \u003Cterm> — \u003Cdefinition>.`\n8. **Append under `## Glossary`.** Read the file, insert the line in `## Glossary` (alphabetical if the section is already sorted, else at the end). Never rewrite existing entries.\n9. **Prune empty H2s.** On a fresh bootstrap, delete `## Invariants` \u002F `## Out of scope` if they hold no real content — only `## Glossary` is mandatory. (A genuine invariant or out-of-scope note goes in its section, never as implementation detail.)\n10. **Stamp + commit + handoff.** Set `updated_at: \u003Ctoday>` in the frontmatter. Propose `context: + \u003Cterm>` (or `context: + \u003Cterm>, \u003Cterm2>` for a batch). May fold into the caller's intake\u002FPRD commit. Then **emit the stage-handoff block** per [`..\u002F_shared\u002Fhandoff.md`](..\u002F_shared\u002Fhandoff.md) (utility variant) — *What I did* + *Review* (`CONTEXT.md`) + *Run next*: resume your backbone stage (e.g. `\u002Fsdlc:architecture-design \u003Cslug>`); `\u002Fclear` optional.\n\n## Definition of Done\n\n- `\u003Ctarget>` exists and contains `\u003Cterm>` under `## Glossary` in the «one-sentence canonical + optional NOT-reference» format.\n- Any conflict with an existing entry is resolved (reported as duplicate, or disambiguated into distinct names).\n- Generic tech words are refused, not stored.\n- Empty H2 sections are pruned on bootstrap; `## Glossary` remains.\n- Multi-context: `CONTEXT-MAP.md` has a row for the context; the term lands in the correct bounded-context `CONTEXT.md`.\n- `updated_at` reflects today; a commit is proposed.\n\n## Anti-patterns\n\n- **Glossary as PRD or scratch pad.** Implementation detail («counter stored with a 1-minute TTL») belongs in the SAD\u002FADR, not here.\n- **Empty H2 «for completeness».** A heading with no bullets — prune it.\n- **Silent edits.** Adding a term without confirming the definition; the author must control the glossary.\n- **Batched «I'll add them later».** Capture each term the moment it surfaces — deferral loses it.\n- **Storing generic tech words.** HTTP, queue, the datastore name — refuse them.\n- **Rewriting on re-run.** The skill reads and appends; it never overwrites the file.\n- **Ambiguous term with no NOT-reference.** A homonym without «NOT …» is a six-month confusion waiting to happen.\n- **Multi-context term in the wrong file.** When `CONTEXT-MAP.md` exists, each term must land in the file that owns its bounded context — not always the root.\n\n## References & templates\n\n- [`.\u002Ftemplates\u002FCONTEXT.md`](.\u002Ftemplates\u002FCONTEXT.md) — output scaffold; inline comments are the per-section contract (Glossary mandatory, Invariants\u002FOut-of-scope pruned when empty).\n- [`..\u002F_shared\u002Fask-style.md`](..\u002F_shared\u002Fask-style.md) — phrasing for the definition \u002F NOT-reference \u002F conflict questions.\n- [`..\u002F_shared\u002Fhandoff.md`](..\u002F_shared\u002Fhandoff.md) — stage-handoff block format (utility variant).\n- [`..\u002F..\u002F..\u002Fdocument-templates\u002FCONTEXT-MAP.md`](..\u002F..\u002F..\u002Fdocument-templates\u002FCONTEXT-MAP.md) — CONTEXT-MAP.md scaffold for multi-context repos.\n\n## Example invocation\n\n> **User:** «add term tenant for rate-limiting-per-user»\n> **Skill:** `test -f CONTEXT-MAP.md` → not exists. Single-context. `\u003Cslug>` = `rate-limiting-per-user` → target `docs\u002Ffeatures\u002Frate-limiting-per-user\u002FCONTEXT.md`. Generic filter: `tenant` is domain → continue. File missing → copy template. `grep \"^- tenant\"` → not found. Definition Q → «a billable customer organisation owning 1+ users». NOT-reference Q → «NOT user — a user is one person inside a tenant». Compose `- tenant — a billable customer organisation owning 1+ users. NOT user (a user is one person inside a tenant).` → append under `## Glossary` → prune empty `## Invariants`\u002F`## Out of scope` → `updated_at: 2026-05-29` → commit `context: + tenant`. Emit handoff block (utility variant): *What I did* — appended `tenant` to `docs\u002Ffeatures\u002Frate-limiting-per-user\u002FCONTEXT.md`; *Run next* — resume `\u002Fsdlc:architecture-design rate-limiting-per-user`.\n","# Skill: fix-term\n\nLazy utility that fixes the meaning of a domain term in `CONTEXT.md` the moment it first surfaces, so its sense doesn't drift across the pipeline. For each term it captures a one-sentence canonical definition and — when the word is ambiguous — a **NOT-reference** naming the concept it's confused with. Runs anytime, with no upstream gate: a single term mid-interview, or a batch handed over by `write-prd`. The output feeds `write-prd` (role + domain-term names) and `architecture-design` (invariants), which treat `## Glossary` as canonical and override anything that contradicts it.\n\nThis is a capture utility, not a Socratic stage — it does **not** run the shared Socratic loop or critic. The one shared dependency is question phrasing:\n→ [`..\u002F_shared\u002Fask-style.md`](..\u002F_shared\u002Fask-style.md)\n\n## Owner\n\nWhoever drives the conversation — anyone who spots ambiguity. Tech Lead approves the canonical form when a term is contested.\n\n## Inputs\n\n- `\u003Cterm>` — the domain word\u002Fphrase to fix. If not given, ask for it.\n- (Optional) `\u003Cslug>` — feature slug; targets `docs\u002Ffeatures\u002F\u003Cslug>\u002FCONTEXT.md`. Absent → single-context check below.\n- (Optional) `\u003Ccontext>` — bounded-context name (for multi-context repos); detected via `CONTEXT-MAP.md`.\n- (Optional) `pending_glossary_terms` — a batch handed over by `write-prd` after it writes the PRD. Process each term in turn.\n- (Optional) proposed phrasings already surfaced in an interview\u002Fbrainstorm — offer them as definition options instead of asking blank.\n\n## Protocol\n\n1. **Detect context mode.** `test -f CONTEXT-MAP.md` at the repo root.\n   - **Multi-context** (file exists and contains real rows): ask which bounded context `\u003Cterm>` belongs to: «Available contexts: `\u003Clist from CONTEXT-MAP.md>`.» (phrasing per [`..\u002F_shared\u002Fask-style.md`](..\u002F_shared\u002Fask-style.md)). Target `\u003Cctx>\u002FCONTEXT.md`. If the context isn't yet registered in CONTEXT-MAP.md, add a row now (`| \u003Cctx> | \u003Cpath> | \u003C1-line scope> |`).\n   - **Single-context** (no CONTEXT-MAP.md or only a stub): if `\u003Cslug>` is given → `docs\u002Ffeatures\u002F\u003Cslug>\u002FCONTEXT.md`; otherwise → repo-root `CONTEXT.md`. One glossary per file; don't split a term across both.\n2. **Generic-term filter.** Reject words that name infrastructure or transport rather than the business domain (e.g. HTTP, queue, cache, the datastore, a framework, JSON, REST, gRPC). Refuse: «`\u003Cterm>` is technical, not a domain word — its choice belongs in the SAD or an ADR, not the glossary». Continue only for genuine domain vocabulary.\n3. **Bootstrap (lazy).** `test -f \u003Ctarget>`. Missing → copy [`.\u002Ftemplates\u002FCONTEXT.md`](.\u002Ftemplates\u002FCONTEXT.md) to `\u003Ctarget>`. Present → read it.\n4. **Conflict check.** `grep -i \"^- \u003Cterm>\" \u003Ctarget>`.\n   - Found, identical sense → STOP, report «already in the glossary».\n   - Found, different sense → escalate via `AskUserQuestion` (phrasing per [`..\u002F_shared\u002Fask-style.md`](..\u002F_shared\u002Fask-style.md)): «`\u003Cterm>` is already defined as `\u003Cexisting>` — same concept or a different one?». If different, propose a disambiguating pair of names (e.g. a billing-scoped vs a runtime-scoped variant) and fix both.\n   - Not found → continue.\n5. **Ask the canonical definition** — one `AskUserQuestion`: «Define `\u003Cterm>` in this domain, in one sentence». Offer interview\u002Fbrainstorm phrasings as options when available; otherwise free text. Follow the explanatory style in [`..\u002F_shared\u002Fask-style.md`](..\u002F_shared\u002Fask-style.md) — gloss every technical term inline, explain why the definition matters.\n6. **Ask the NOT-reference** — one `AskUserQuestion`: «Which concept does `\u003Cterm>` get confused with, so a future reader doesn't mix them up?». No plausible homonym → `None`.\n7. **Compose one line.** `- \u003Cterm> — \u003Cone-sentence definition>. NOT \u003Cconfused concept + how it differs>.` — or, when step 6 = None, `- \u003Cterm> — \u003Cdefinition>.`\n8. **Append under `## Glossary`.** Read the file, insert the line in `## Glossary` (alphabetical if the section is already sorted, else at the end). Never rewrite existing entries.\n9. **Prune empty H2s.** On a fresh bootstrap, delete `## Invariants` \u002F `## Out of scope` if they hold no real content — only `## Glossary` is mandatory. (A genuine invariant or out-of-scope note goes in its section, never as implementation detail.)\n10. **Stamp + commit + handoff.** Set `updated_at: \u003Ctoday>` in the frontmatter. Propose `context: + \u003Cterm>` (or `context: + \u003Cterm>, \u003Cterm2>` for a batch). May fold into the caller's intake\u002FPRD commit. Then **emit the stage-handoff block** per [`..\u002F_shared\u002Fhandoff.md`](..\u002F_shared\u002Fhandoff.md) (utility variant) — *What I did* + *Review* (`CONTEXT.md`) + *Run next*: resume your backbone stage (e.g. `\u002Fsdlc:architecture-design \u003Cslug>`); `\u002Fclear` optional.\n\n## Definition of Done\n\n- `\u003Ctarget>` exists and contains `\u003Cterm>` under `## Glossary` in the «one-sentence canonical + optional NOT-reference» format.\n- Any conflict with an existing entry is resolved (reported as duplicate, or disambiguated into distinct names).\n- Generic tech words are refused, not stored.\n- Empty H2 sections are pruned on bootstrap; `## Glossary` remains.\n- Multi-context: `CONTEXT-MAP.md` has a row for the context; the term lands in the correct bounded-context `CONTEXT.md`.\n- `updated_at` reflects today; a commit is proposed.\n\n## Anti-patterns\n\n- **Glossary as PRD or scratch pad.** Implementation detail («counter stored with a 1-minute TTL») belongs in the SAD\u002FADR, not here.\n- **Empty H2 «for completeness».** A heading with no bullets — prune it.\n- **Silent edits.** Adding a term without confirming the definition; the author must control the glossary.\n- **Batched «I'll add them later».** Capture each term the moment it surfaces — deferral loses it.\n- **Storing generic tech words.** HTTP, queue, the datastore name — refuse them.\n- **Rewriting on re-run.** The skill reads and appends; it never overwrites the file.\n- **Ambiguous term with no NOT-reference.** A homonym without «NOT …» is a six-month confusion waiting to happen.\n- **Multi-context term in the wrong file.** When `CONTEXT-MAP.md` exists, each term must land in the file that owns its bounded context — not always the root.\n\n## References & templates\n\n- [`.\u002Ftemplates\u002FCONTEXT.md`](.\u002Ftemplates\u002FCONTEXT.md) — output scaffold; inline comments are the per-section contract (Glossary mandatory, Invariants\u002FOut-of-scope pruned when empty).\n- [`..\u002F_shared\u002Fask-style.md`](..\u002F_shared\u002Fask-style.md) — phrasing for the definition \u002F NOT-reference \u002F conflict questions.\n- [`..\u002F_shared\u002Fhandoff.md`](..\u002F_shared\u002Fhandoff.md) — stage-handoff block format (utility variant).\n- [`..\u002F..\u002F..\u002Fdocument-templates\u002FCONTEXT-MAP.md`](..\u002F..\u002F..\u002Fdocument-templates\u002FCONTEXT-MAP.md) — CONTEXT-MAP.md scaffold for multi-context repos.\n\n## Example invocation\n\n> **User:** «add term tenant for rate-limiting-per-user»\n> **Skill:** `test -f CONTEXT-MAP.md` → not exists. Single-context. `\u003Cslug>` = `rate-limiting-per-user` → target `docs\u002Ffeatures\u002Frate-limiting-per-user\u002FCONTEXT.md`. Generic filter: `tenant` is domain → continue. File missing → copy template. `grep \"^- tenant\"` → not found. Definition Q → «a billable customer organisation owning 1+ users». NOT-reference Q → «NOT user — a user is one person inside a tenant». Compose `- tenant — a billable customer organisation owning 1+ users. NOT user (a user is one person inside a tenant).` → append under `## Glossary` → prune empty `## Invariants`\u002F`## Out of scope` → `updated_at: 2026-05-29` → commit `context: + tenant`. Emit handoff block (utility variant): *What I did* — appended `tenant` to `docs\u002Ffeatures\u002Frate-limiting-per-user\u002FCONTEXT.md`; *Run next* — resume `\u002Fsdlc:architecture-design rate-limiting-per-user`.\n",{"name":5,"triggers":24,"description":7},[25,26,27,28,29,30,31,32,33],"\u002Fsdlc:fix-term","fix term","add term","what is X in our domain","add to CONTEXT","fix the glossary","define X","додай термін","онови глосарій","main","2dc9bdfa5d508a04d414fb0991617e6722ec635a","modules\u002F6-sdlc\u002Fsdlc\u002Fplugin\u002Fskills\u002Ffix-term",13,"https:\u002F\u002Fgithub.com\u002Fgenkovich\u002Fagentic-engineering-course-public","https:\u002F\u002Ft.me\u002Fgenkovich","https:\u002F\u002Fgithub.com\u002Fgenkovich","https:\u002F\u002Ft.me\u002Fbeerphp","Beer::PHP 🍺 telegram-channel author \r\n","2026-11-12 03:03:13",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add genkovich\u002Fagentic-engineering-course-public --skill fix-term",{"tool":50,"command":51},"bunx","bunx skills add genkovich\u002Fagentic-engineering-course-public --skill fix-term",{"tool":53,"command":54},"pnpm","pnpm dlx skills add genkovich\u002Fagentic-engineering-course-public --skill fix-term","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgenkovich\u002Fagentic-engineering-course-public\u002Fblob\u002Fmain\u002Fmodules\u002F6-sdlc\u002Fsdlc\u002Fplugin\u002Fskills\u002Ffix-term\u002FSKILL.md",true,[58],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"templates\u002FCONTEXT.md","REFERENCE","参考文档",1735,"https:\u002F\u002Fgithub.com\u002Fgenkovich\u002Fagentic-engineering-course-public\u002Fblob\u002Fmain\u002Fmodules\u002F6-sdlc\u002Fsdlc\u002Fplugin\u002Fskills\u002Ffix-term\u002Ftemplates\u002FCONTEXT.md",[65,73,80,87,94,101],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":72},"01M72YGBW5JKECT8WSRHK1YBCJ","release","Run the whole local release pipeline in order, stopping at each human gate. Triggers on \"run the release\", \"prepare a release\", \"\u002Frelease\", \"зроби реліз\", \"підготуй реліз\". Drives the four stages back to back — bump-version → curate-changelog → release-notes → check-docs-drift — pausing after each so the human reviews the diff before the next stage. Prepares everything in the working tree; never tags, commits, or pushes. The tag push (which fires CI) stays the human's action.","https:\u002F\u002Fgithub.com\u002Fgenkovich\u002Fagentic-engineering-course-public\u002Fblob\u002Fmain\u002Fmodules\u002F9-collaboration\u002F9.7-release-docs\u002F.claude\u002Fskills\u002Frelease\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":72},"01M72YG87VQ89PRCYQSMNAP5RW","release-notes","Draft partner-facing release notes from the same commits as the changelog. Triggers on \"draft release notes\", \"release notes for the next version\", \"\u002Frelease-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.","https:\u002F\u002Fgithub.com\u002Fgenkovich\u002Fagentic-engineering-course-public\u002Fblob\u002Fmain\u002Fmodules\u002F9-collaboration\u002F9.7-release-docs\u002F.claude\u002Fskills\u002Frelease-notes\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":72},"01M72YG4BXJH9R6QQZD3G8E358","curate-changelog","Curate the [Unreleased] section of docs\u002FCHANGELOG.md from git history. Triggers on \"curate the changelog\", \"update the changelog\", \"\u002Fcurate-changelog\", \"онови changelog\", \"курування журналу\". Reads git log since the last tag, FILTERS out what a reader never feels (test\u002Fci\u002Fchore\u002Fmerge), GROUPS commits about one feature into one bullet, and REWRITES technical subjects into plain language under the six Keep a Changelog categories (Added\u002FChanged\u002FDeprecated\u002F Removed\u002FFixed\u002FSecurity). 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.","https:\u002F\u002Fgithub.com\u002Fgenkovich\u002Fagentic-engineering-course-public\u002Fblob\u002Fmain\u002Fmodules\u002F9-collaboration\u002F9.7-release-docs\u002F.claude\u002Fskills\u002Fcurate-changelog\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":72},"01M72YFZDKNXQ7WF9ARC5KQ4F5","codify-rule","Turn a repeated mistake into a durable, path-scoped rule in .claude\u002Frules\u002F. Triggers on \"codify this rule\", \"make a rule so this doesn't happen again\", \"\u002Fcodify-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\u002Frules\u002F; never commits or pushes.","https:\u002F\u002Fgithub.com\u002Fgenkovich\u002Fagentic-engineering-course-public\u002Fblob\u002Fmain\u002Fmodules\u002F9-collaboration\u002F9.7-release-docs\u002F.claude\u002Fskills\u002Fcodify-rule\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":72},"01M72YFVKC19NCQDD30R1C282Q","check-docs-drift","Find and fix where docs\u002Fapi.md fell behind the code. Triggers on \"check for doc drift\", \"is the API doc up to date\", \"\u002Fcheck-docs-drift\", \"перевір дрейф документації\", \"docs drift\". Runs the deterministic scripts\u002Fcheck-docs-drift.py (parses the public NoteBook methods with ast, compares to what docs\u002Fapi.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\u002F; never commits or pushes.","https:\u002F\u002Fgithub.com\u002Fgenkovich\u002Fagentic-engineering-course-public\u002Fblob\u002Fmain\u002Fmodules\u002F9-collaboration\u002F9.7-release-docs\u002F.claude\u002Fskills\u002Fcheck-docs-drift\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":72},"01M72YFQSJ21QX4SQADQ1SQDZR","bump-version","Decide and apply the next semver for a release. Triggers on \"bump the version\", \"what version is next\", \"\u002Fbump-version\", \"простав версію\", \"яка наступна версія\". Reads the next number from the deterministic scripts\u002Fnext-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.","https:\u002F\u002Fgithub.com\u002Fgenkovich\u002Fagentic-engineering-course-public\u002Fblob\u002Fmain\u002Fmodules\u002F9-collaboration\u002F9.7-release-docs\u002F.claude\u002Fskills\u002Fbump-version\u002FSKILL.md",[],[]]