菜单
Use when the user asks "обнови changelog / добавь запись в changelog", or after a user-visible change is committed. Also trigger automatically after a `feat:` or `fix:` commit. SKIP: for `chore:`, `docs:`, `test:`, `refactor:`, `style:`, `ci:`, `build:` commits unless the change is user-facing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | changelog-entry |
| version | 1.0.0 |
| description | Use when the user asks "обнови changelog / добавь запись в changelog", or after a user-visible change is committed. Also trigger automatically after a `feat:` or `fix:` commit. SKIP: for `chore:`, `docs:`, `test:`, `refactor:`, `style:`, `ci:`, `build:` commits unless the change is user-facing. |
| category | code |
| tags | ["changelog","keep-a-changelog","russian"] |
Add an entry to the repo's root CHANGELOG.md following Keep a Changelog format, in Russian.
CHANGELOG.md.## [Unreleased] section.feat: → ### Добавленоfix: → ### Исправлено### Удалено### Изменено[Unreleased] is mutable).Updated CHANGELOG.md content (full file) or a unified diff.
Ask the user to confirm before writing.
Use when a request leaves material product, architecture, behavior, or scope decisions unresolved. Do NOT use for approved, well-bounded implementation work.
Use when 2 or more substantial tasks are independent, have disjoint state, and parallel execution will save meaningful time. Do NOT use for coupled or sequential work.
Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.
Use when verified implementation is ready and the user must choose whether to keep, merge, or publish the branch. Do NOT use before applicable checks pass.
Use when receiving code review feedback that may be unclear or technically questionable and needs verification. Do NOT use for an unrequested general code review.
Use when a completed change is high-risk, crosses subsystem boundaries, or the user explicitly requests independent review. Do NOT use by default for low- or medium-risk changes.