Detailed PR Description

Workflow

Use this skill when the user asks for a detailed PR description, a PR body rewrite, or an assessment of whether the branch's tests are strong enough to catch regressions.

1. Identify the PR and its comparison base.

   • Prefer gh pr view --json number,title,body,baseRefName,headRefName,url when a PR exists.
   • If there is no PR, compare against the repository's default base branch or the user-provided base and prepare a PR description draft instead of stopping.
   • Fetch the base branch if needed before relying on diffs.

2. Build the context from tracked project artifacts.

   • Inspect git status --short, git diff --stat <base>...HEAD, git diff --name-only <base>...HEAD, relevant commits, changed files, tests, docs, migrations, config, and generated artifacts that are part of the branch.
   • Read .context/ only as local scratch context. Anything important from .context/ must be restated in the PR description because .context/ is not tracked.
   • Do not rely on memory or prior chat alone for claims about behavior.