describe-prlisted

# Generate PR Description !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh describe-pr` **PRs directory**: !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh prs` **Tmp directory**: !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh tmp` **IMPORTANT**: Wherever `{prs directory}` or `{tmp directory}` appears in the instructions below, substitute the actual resolved path shown above. **PR description template**: !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-template.sh pr-description` You are tasked with generating a comprehensive pull request description following the repository's standard template. ## Steps to follow: ### Step 1: Use the PR description template - The template is shown above under "PR description template" - Read the template carefully to understand all sections and requirements ### Step 2: Identify the PR to describe - Check if the current branch has an associated PR: `gh pr view --json url,number,title,state 2>/dev/null` - If no PR exists for the current branch, or if on main/master, list open PRs: `gh pr list --limit 10 --json number,title,headRefName,author` - Ask the user which PR they want to describe ### Step 3: Check for existing description - Check if `{prs directory}/{number}-description.md` already exists - If it exists, read it and inform the user you'll be updating it - Consider what has changed since the last description was written ### Step 4: Gather comprehens