🤖 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:
mainormaster, detect fromgh repo view) - Draft mode (optional, default: off)
- Template (optional): if
.github/pull_request_template.mdexists, use its section headings
Workflow
1. Gather branch context
# 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> --name-status
git diff <base>...<head> --numstat
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. Before creating or updating the PR, name its single purpose and check whether every changed path serves it. Call out unrelated formatting, generated files, or a second feature. Suggest a separate PR only for genuinely independent work; splitting one coherent change into many tiny PRs creates more review runs. Do not rewrite commits or remove files without authorization.
Check the applicable AGENTS.md files: the repository root and nested files covering changed
paths. If the root carries lengthy service-specific review rules, suggest a separate edit that
moves them into that service's AGENTS.md. Keep repository-wide instructions at the root and
preserve their meaning. Do not automatically delete or shorten existing policy to save tokens.
2. Check for existing PR
gh pr view --json number,title,body,state 2>/dev/null
- If a PR exists in
OPENstate: update it withgh pr edit. - If no PR exists: create one with
gh pr create.
3. Check for a PR template
cat .github/pull_request_template.md 2>/dev/null \
|| cat .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null \
|| cat PULL_REQUEST_TEMPLATE.md 2>/dev/null
If a template exists, mirror its section headings and populate them. Skip sections that ask for credentials, tokens, internal hostnames, or content unrelated to the diff.
4. Draft title and body
Title rules:
- Use Conventional Commits prefix when the branch/commits use it:
feat(scope):,fix:, etc. - ≤ 70 characters
- Imperative mood ("Add X", "Fix Y", not "Added X")
- Include ticket number if present in branch name (e.g.
LIN-123,GH-456)
Body sections (use the template if one was found, otherwise use this structure):
## Summary
- <bullet: what changed>
- <bullet: why>
## Changes
- `<file or subsystem>`: <what changed and why>
## Test plan
- [ ] <what to run and what result to expect>
- [ ] <manual steps if automated tests don't cover it>
## Notes
<optional: anything a reviewer should watch for, known gaps, follow-up issues>
For a PR likely to receive Codex review, use Notes to state its review scope. Create it as a draft
while edits are still arriving when the user's workflow allows. When the branch is ready, use
codexloop's review-state check before requesting review. Check the selected repository under
ChatGPT Settings → Code Review: repository-level automatic review can override personal
preferences, and its scope and trigger determine whether this PR should already be reviewed. If
automatic review is on for this PR, wait for it; if status is unknown, verify the repository
setting; if it is off, request one review only when Codex has not reviewed the current head and no
request is already pending. The minimum reporting severity controls which findings Codex reports;
do not describe it as reducing compute or usage without evidence. Check whether automatic security
review is enabled too, since it may run whenever code review runs.
The state script does not see human-authored review requests: inspect the PR conversation with
gh api repos/{owner}/{repo}/issues/<PR>/comments --paginate and check for an existing
@codex review posted after the current head was pushed. If one exists, wait for it; do not post
another.
Do not add a review mention on PR creation or after every push.
Rules:
- Describe intent, not what the diff already shows line-by-line.
- If commits already have good conventional messages, use them as the skeleton.
- Skip any section that has nothing meaningful to say.
- Reference specific files, functions, or lines only when they aid navigation.
5. Create or update the PR
Always pass the body via a heredoc or temp file: never interpolate it into the command string (quotes and newlines will break the shell):
# Create new PR
gh pr create \
--title "<title>" \
--body "$(cat <<'PRBODY'
<body>
PRBODY
)" \
--base <base> \
[--draft]
# Update existing PR
gh pr edit <number> \
--title "<title>" \
--body "$(cat <<'PRBODY'
<body>
PRBODY
)"
6. Confirm and report
gh pr view --json number,title,url -q '"PR #\(.number): \(.title)\n\(.url)"'
Print the PR number, title, and URL. If the PR was newly created, note whether CI triggered automatically.
Chaining
| Before this skill | After this skill |
|---|---|
olko:git-commit + git push |
olko:qodoloop |
git push -u origin <branch> |
olko:coderabbitloop |
| N/A | olko:open-source-publisher (for new repos) |
