ru-commit-message
Use when the user asks "напиши коммит / сгенерь commit message / опиши этот diff as commit". Also trigger automatically before `git commit` if no message was provided. SKIP: if the user already wrote a commit message, or for trivial merge/revert commits.
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 16
- Forks
- 5
01 前言 Front Matter
- name
- ru-commit-message
- tags
- [ "git", "conventional-commits", "russian" ]
- version
- 1.0.0
- category
- code
- description
- Use when the user asks "напиши коммит / сгенерь commit message / опиши этот diff as commit". Also trigger automatically before `git commit` if no message was provided. SKIP: if the user already wrote a commit message, or for trivial merge/revert commits.
02 资源文件 3
- 参考文档CHANGELOG.md606 B
- 参考文档README.md1.3 KB
- 参考文档references/examples.md2.0 KB
03 SKILL.md 正文
Purpose
Generate a conventional-commit message in Russian from the current staged diff.
Process
- Run
git diff --stagedto read what's actually being committed. - Classify the change:
feat/fix/chore/refactor/docs/test/style/perf/ci/build. - Pick scope (optional) — module or component name, lowercase, English, from changed file paths.
- Write the description in Russian, imperative mood, lowercase start, no trailing period, ≤72 chars.
- If the change is non-trivial — add a body paragraph in Russian explaining WHY, not WHAT. Wrap at ~72 chars.
- Output the message ready to paste into
git commit -m.
Format
<type>(<scope>): <описание на русском>
<опциональное тело на русском, объясняет ПОЧЕМУ>
Examples
See references/examples.md.
Anti-patterns
- Body explaining WHAT changed (diff already shows that).
- Description in English.
- Description over 72 chars.
- Including file paths in the description when scope already covers it.
04 同仓库更多 Skills
bad
暂无简介
writing-skills
Use when creating, editing, or validating reusable agent skills and their trigger behavior. Do NOT use for ordinary project documentation or one-off prompts.
writing-plans
Use when an approved change spans multiple dependent outcomes and needs a durable implementation sequence before coding. Do NOT use for small, obvious, reversible edits.
verification-before-completion
Use when about to claim work is complete, fixed, passing, or ready to integrate. Do NOT use to repeat checks without a completion claim or concrete doubt.
using-superpowers
Use when starting a conversation or deciding whether a Superpowers workflow matches the current task. Do NOT use it to auto-invoke skills whose stated triggers do not match.
using-git-worktrees
Use when feature work needs isolation from the current workspace or before executing a risky implementation plan. Do NOT use when the current workspace is already safe and isolated.