describe-pr

You are tasked with generating a comprehensive pull request description following the repository's standard template. Read the PR description template: Identify the PR to describe: Check for existing description: Gather comprehensive PR information: 4b. Gather reasoning history (if available): Analyze the changes thoroughly: (ultrathink about the code changes, their architectural implications, and potential impacts) Handle verification requirements: Generate the description: Save the description: Update the PR: - Read the PR description template: - First, check if thoughts/shared/pr_description.md exists - If it doesn't exist, inform the user they need to create a PR description template at thoughts/shared/pr_description.md - Read the template carefully to understand all sections and requirements - 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 - Check for existing description: - Check if thoughts/shared/prs/{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 - Gather comprehensive PR...