메뉴
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".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | ru-pr-description |
| version | 1.0.0 |
| 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". |
| category | code |
| tags | ["git","github","pr","russian"] |
Generate a Russian PR title + description from the branch diff and commit history.
main by 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.## TL;DR
<1–2 предложения: что и зачем>
## Что изменилось
- <пункт>
- <пункт>
## Как тестировал
- <команды или ручные шаги>
- <результат>
## Чек-лист
- [x] Тесты проходят
- [x] Линтер чист
- [ ] Changelog обновлён (если есть user-visible изменения)
- [ ] Документация обновлена (если изменился публичный API)
Full title + body text, ready to paste into gh pr create --title "..." --body "..." or the GitHub UI.
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.