Опишете задачата
Към всички skills

pr-description-writer

mohitagw15856 · Документация

Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance.

Оригинален текст · няма потвърден превод на български
Платформи: ClaudeНиво: СредноВ индекса: 04.03.2026 г.Обновен в GitHub: 09.06.2026 г.

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md
GitHub хранилище
Звезди на репото
1392
Лиценз
Не е посочен. Проверете в репозитория.
Последна проверка на записа
Няма посочена дата

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add mohitagw15856/pm-claude-skills

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.md

Началото на файла на автора, без превод.

PR Description Writer Skill

Writes structured, reviewer-friendly pull request descriptions from a diff, commit list, or informal notes. Covers the what, why, and how-to-review so reviewers can start immediately.

Not quite this? Use pr-description-live when you want it to read the real diff through the GitHub connector.

Required Inputs

Ask for these if not provided:

  • What changed (paste a git diff, git log --oneline, or describe the changes in plain English)
  • Why it was changed (the problem being solved or feature being added)
  • How to test it (any specific steps a reviewer needs to verify it works)
  • Risk level (low / medium / high — affects how much reviewer guidance to include)
  • PR type (feature / bug fix / refactor / dependency upgrade / config change / hotfix)
  • Target branch (e.g. main / develop / release/2.4 — affects risk framing and reviewer guidance)
  • Linked issue or ticket (e.g. JIRA-1234, GitHub #567 — or "none")

Output Format

Title

A clear, imperative-mood title under 72 characters: [type]: [concise description of what changed]

Examples:

  • feat: add rate limiting to the public API
  • fix: resolve race condition in session expiry
  • refactor: extract payment logic into PaymentService

Summary

2–3 sentences covering:

  • What this PR does (the change)
  • Why it was needed (the problem or goal)
  • The approach taken (at a high level)

Changes Made

Bullet list of specific changes — one bullet per logical change, not per file:

  • Added [X] to handle [Y]
  • Refactored [A] to reduce [B]
  • Removed [C] as it was replaced by [D]
  • Updated [E] to fix [F]

Screenshots / Demo

[If UI change: include before/after screenshots or a screen recording] [If API change: include example request/response] [If no visual change and no API contract change: omit this section entirely — do not leave it as a placeholder]

How to Test

Step-by-step instructions a reviewer can follow:

  1. [Setup step if needed]
  2. [Action to take]
  3. [What to verify]
  4. [Edge case to check]

Include any specific commands, test data, or environment flags needed.

Testing Checklist

  • Unit tests added/updated
  • Integration tests added/updated
  • Edge cases covered
  • Manual testing completed
  • No regressions in existing tests

Целият SKILL.md в GitHub