← ClaudeAtlas

namht-prlisted

Prepare or review a Pull Request. PREPARE mode: from the current branch's diff + commits, draft a PR title and description (what/why, changes, risk + blast radius, tests done, checklist). REVIEW mode: given a PR number/URL, pull its diff (gh pr diff) and run a two-phase review (quality checklist + business consistency vs KB) with blast-radius (callers) analysis. Use when the user says "/pr", "prepare a PR", "write PR description", "review PR 123", "review this pull request". Does not push/merge.
NamHT4Devlop/nam-claude-skill · ★ 0 · Code & Development · score 72
Install: claude install-skill NamHT4Devlop/nam-claude-skill
# namht-pr — prepare or review a Pull Request Two modes (pick from the argument / context). Read-only on the remote: it **drafts** or **reviews**; it never pushes, merges, or creates the PR unless the user explicitly asks (and the git-guard hook blocks remote-mutating git anyway). Read/Grep for impact, KB for business consistency. ## Mode A — PREPARE a PR (default; from the current branch) 1. **Gather the change.** `git diff <base>...HEAD` (base = the default branch, or one the user names) + `git log <base>..HEAD` for the commits + `git diff --stat`. (All read-only git — allowed.) 2. **Assess impact.** **Grep for callers** of the changed symbols → downstream consumers & any with no covering tests. Ground business effects in the KB (flows/rules touched). 3. **Draft the PR** (dual-audience Markdown, ready to paste): ``` # <type(scope): concise title> ## Summary (plain language) ← what & why, for any reviewer ## Changes ← bullet list of the meaningful changes (files/areas) ## Impact & risk ← blast radius (who/what is affected), breaking changes, migrations ## How it was tested ← tests added/run + results; gaps ## Checklist ← [ ] tests pass [ ] no secrets [ ] docs/KB updated [ ] follows architecture ## Notes for reviewers ← anything non-obvious to look at ``` Save to `namht-sessions/pr/<branch>-<date>.md`. Offer to open `gh pr create` with