pr-description-writerlisted

Draft and post a GitHub PR title and body from git diff and commit history. Use when opening a new PR, when the user asks to "write a PR description", "draft a PR", "open a PR for this branch", or after running the git-commit skill and pushing the branch. Chains naturally after git-commit and before qodoloop / coderabbitloop.
oleg-koval/agent-skills · ★ 3 · AI & Automation · score 75

Install: claude install-skill oleg-koval/agent-skills

> 🤖 *Auto-generated by **weekly-pattern-learner** · qodoloop and coderabbitloop both open with `gh pr view`: the PR creation/description step was never codified as its own skill* # PR Description Writer Draft a GitHub-ready PR title and body from the branch's commit history and diff, then create or update the PR so reviewers and AI tools have full context. ## Inputs - **Base branch** (optional, default: `main` or `master`, detect from `gh repo view`) - **Draft mode** (optional, default: off) - **Template** (optional): if `.github/pull_request_template.md` exists, use its section headings ## Workflow ### 1. Gather branch context ```bash # Current branch git rev-parse --abbrev-ref HEAD # Base branch gh repo view --json defaultBranchRef -q '.defaultBranchRef.name' # Commits since base git log <base>..<head> --oneline --no-merges # Diff summary (full diff for small PRs, stat-only for large) git diff <base>..<head> --stat git diff <base>..<head> # only if total changes < ~500 lines ``` If the diff is large (>500 changed lines), read file-by-file rather than all at once. ### 2. Check for existing PR ```bash gh pr view --json number,title,body,state 2>/dev/null ``` - If a PR exists in `OPEN` state: update it with `gh pr edit`. - If no PR exists: create one with `gh pr create`. ### 3. Check for a PR template ```bash cat .github/pull_request_template.md 2>/dev/null \ || cat .github/PULL_REQUES