describe_pr

Generate PR Description

You are tasked with generating a comprehensive pull request description following the repository's standard template.

User message (if any): $ARGUMENTS

Steps to follow:

1. Get the PR description template:

   • Call tools_thoughts_get_template with template=pr_description
   • Read the template carefully to understand all sections and requirements

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

3. Check for existing description (MCP):

   • Call tools_thoughts_list_documents and filter doc_type = "artifacts" with filename pr_{number}_description.md
   • If found, read it and inform user you'll be updating it
   • Consider what has changed since last description

4. Gather comprehensive PR information:

   • Get the full PR diff: gh pr diff {number}
   • If you see the error "No default remote repository has been set", instruct the user to run gh repo set-default and select the appropriate repository
   • Get commit history: gh pr view {number} --json commits
   • Review the base branch: gh pr view {number} --json baseRefName
   • Get PR metadata: gh pr view {number} --json url,title,number,state

5. Analyze the changes thoroughly: (think deeply about the code changes, their architectural implications, and potential impacts)

   • Read through the entire diff carefully
   • For context, read any files that are referenced but not shown in the diff
   • Understand the purpose and impact of each change
   • Identify user-facing changes vs internal implementation details
   • Look for breaking changes or migration requirements

6. Handle verification requirements:

   • Look for any checklist items in the "How to verify it" section of the template
   • For each verification step:
     • If it's a recipe you can run, use the Just MCP tools:
       • Discover available recipes with tools_cli_just_search (e.g., search for "check", "test")
       • Execute recipes with tools_cli_just_execute (e.g., run the "check" and "test" recipes)
     • If it passes, mark the checkbox as checked: - [x]
     • If it fails, keep it unchecked and note what failed: - [ ] with explanation
     • If it requires manual testing (UI interactions, external services), leave unchecked and note for user
   • Document any verification steps you couldn't complete