ru-pr-description
Use when the user asks "напиши PR / сгенерь PR description / опиши что я делал в этой ветке". Also trigger automatically before `gh pr create` when no `--body` argument was provided. SKIP: if the PR already has a description, or for draft PRs explicitly marked "wip".
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 16
- Forks
- 5
01 前言 Front Matter
- name
- ru-pr-description
- tags
- [ "git", "github", "pr", "russian" ]
- version
- 1.0.0
- category
- code
- description
- Use when the user asks "напиши PR / сгенерь PR description / опиши что я делал в этой ветке". Also trigger automatically before `gh pr create` when no `--body` argument was provided. SKIP: if the PR already has a description, or for draft PRs explicitly marked "wip".
02 资源文件 2
- 参考文档CHANGELOG.md457 B
- 参考文档README.md1.2 KB
03 SKILL.md 正文
Purpose
Generate a Russian PR title + description from the branch diff and commit history.
Process
- Determine the base branch (
mainby default, or from a user-supplied argument). git log --oneline <base>..HEAD— list commits in this branch.git diff <base>...HEAD --stat— files changed.git diff <base>...HEAD— full diff if under ~500 lines; otherwise summarize from stat + commit messages.- Write the title in Russian: one line, under 70 chars.
- Write the body using the template below.
Template (Russian)
## TL;DR
<1–2 предложения: что и зачем>
## Что изменилось
- <пункт>
- <пункт>
## Как тестировал
- <команды или ручные шаги>
- <результат>
## Чек-лист
- [x] Тесты проходят
- [x] Линтер чист
- [ ] Changelog обновлён (если есть user-visible изменения)
- [ ] Документация обновлена (если изменился публичный API)
Output
Full title + body text, ready to paste into gh pr create --title "..." --body "..." or the GitHub UI.
Anti-patterns
- Description in English.
- TL;DR that just lists commit types ("добавлены feat, fix").
- Copying the full diff into the description.
- Skipping the checklist.
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.