pr-descriptionlisted

Generate and update a pull-request description. Use when opening a PR or after a push, or when the user says "write the PR body" / "update the PR description". Fetches the diff, reads the changed files, then writes a structured body - never hand-write it inline.
NAVNAV221/ai-native-codebase · ★ 1 · Code & Development · score 72

Install: claude install-skill NAVNAV221/ai-native-codebase

# PR Description A good PR body is written from the diff, not from memory. This skill reads what actually changed and produces a description a reviewer can trust. ## Steps 1. **Get the diff.** Fetch the full diff for the branch against the base. 2. **Read the changed files** for context the diff alone doesn't show. 3. **Write the body** with these sections: - **What & why** - the change in one paragraph, and the reason for it. - **How** - the approach, and any notable trade-offs. - **Testing** - what you ran, and what you could not verify (state it, don't guess). - **Screenshots** - for any visible UI change. 4. **Update in place** on later pushes rather than opening a new body. ## Rule Never hand-write the body inside `gh pr create`. Generate it here so every PR is described the same way and stays in sync with the diff.