ru-commit-message
/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.
- Author
- tsergeytovarov ↗
- Repository
- ai-settings ↗
- Licence
- MIT
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author 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.
How it works
SKILL.md has no level-two headings · 33 lines, 161 words
SKILL.md preview
--- name: ru-commit-message version: 1.0.0 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. category: code tags: [git, conventional-commits, russian] --- # Purpose Generate a conventional-commit message in Russian from the current staged diff. # Process 1. Run `git diff --staged` to read what's actually being committed. 2. Classify the change: `feat` / `fix` / `chore` / `refactor` / `docs` / `test` / `style` / `perf` / `ci` / `build`. 3. Pick scope (optional) — module or component name, lowercase, English, from changed file paths. 4. Write the description in Russian, imperative mood, lowercase start, no trailing period, ≤72 chars. 5. If the change is non-trivial — add a body paragraph in Russian explaining **WHY**, not WHAT. Wrap at ~72 chars. 6. 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.
Files in this package (4)
- CHANGELOG.md 1 KB
- README.md 1 KB
- SKILL.md 1 KB
- references/examples.md 2 KB
Versions
The database has no other skills named ru-commit-message.
Database snapshot: 13.11.2026 · package version 128fc626b98c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100commit
Write a commit message and create a git commit. Use when the user wants to commit changes, asks for a commit message, or says "commit this" or "make a commit". - 96commit
Use when writing a commit message, or before running `git commit`. - 100create-commit-message
Generate a Conventional Commit message from staged git changes when the user asks to write a commit message, create a commit, or format a commit - 90commit-message
Write a commit message for the staged changes that matches the repo's own style, and commit when asked. Use when asked to "write a commit message", "commit this", "commit my changes" or "what should this commit say". - 100commit-message
Write a git commit message for the current changes and optionally make the commit. Use when the user says "commit this", "write a commit message", "commit my changes", or asks to split work into commits. - 90commit
在 Git 仓库中分析当前变更,生成符合项目规范的 commit message,自动判断单次提交还是按功能拆分多次提交;正常情况全自动不询问,命中异常规则(不能或无须提交的文件等)才请用户确认。 TRIGGER(中文):"提交一下代码""帮我 commit""这次改动提交了吧""生成 commit message 并提交""/commit""按 fix 提交" "先看看变更别提交""改一下上次的 commit"。 DO NOT TRIGGER:用户只想看变更且未表达提交意图(直接执行 git status/diff 即可); push、rebase…