{"id":"describe-pr","name":"describe-pr","summary":"リポジトリテンプレートに従って包括的なPR説明を作成してください","body":"# Generate PR Description\n\nYou are tasked with generating a comprehensive pull request description following the repository's standard template.\n\n## Steps to follow:\n\n1. **Read the PR description template:**\n   - First, check if `thoughts/shared/pr_description.md` exists\n   - If it doesn't exist, inform the user they need to create a PR description template at `thoughts/shared/pr_description.md`\n   - Read the template carefully to understand all sections and requirements\n\n\n2. **Identify the PR to describe:**\n   - Check if the current branch has an associated PR: `gh pr view --json url,number,title,state 2>/dev/null`\n   - 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`\n   - Ask the user which PR they want to describe\n\n3. **Check for existing description:**\n   - Check if `thoughts/shared/prs/{number}_description.md` already exists\n   - If it exists, read it and inform the user you'll be updating it\n   - Consider what has changed since the last description was written\n\n4. **Gather comprehensive PR information:**\n   - Get the full PR diff: `gh pr diff {number}`\n   - If you get an error about no default remote repository, instruct the user to run `gh repo set-default` and select the appropriate repository\n   - Get commit history: `gh pr view {number} --json commits`\n   - Review the base branch: `gh pr view {number} --json baseRefName`\n   - Get PR metadata: `gh pr view {number} --json url,title,number,state`\n\n4b. **Gather reasoning history (if available):**\n   - Check if reasoning files exist: `ls .git/claude/commits/*/reasoning.md 2>/dev/null`\n   - If they exist, aggregate them: `bash \"$CLAUDE_PROJECT_DIR/.claude/scripts/aggregate-reasoning.sh\" main`\n   - This shows what approaches were tried before the final solution\n   - Save the output for inclusion in the PR description\n\n5. **Analyze the changes thoroughly:** (ultrathink about the code changes, their architectural implications, and potential impacts)\n   - Read through the entire diff carefully\n   - For context, read any files that are referenced but not shown in the diff\n   - Understand the purpose and impact of each change\n   - Identify user-facing changes vs internal implementation details\n   - Look for breaking changes or migration requirements\n\n6. **Handle verification requirements:**\n   - Look for any checklist items in the \"How to verify it\" section of the template\n   - For each verification step:\n     - If it's a command you can run (like `make check test`, `npm test`, etc.), run it\n     - If it passes, mark the checkbox as checked: `- [x]`\n     - If it fails, keep it unchecked and note what failed: `- [ ]` with explanation\n     - If it requires manual testing (UI interactions, external services), leave unchecked and note for user\n   - Document any verification steps you couldn't complete\n\n7. **Generate the description:**\n   - Fill out each section from the template thoroughly:\n     - Answer each question/section based on your analysis\n     - Be specific about problems solved and changes made\n     - Focus on user impact where relevant\n     - Include technical details in appropriate sections\n     - Write a concise changelog entry\n   - **If reasoning files were found (from step 4b):**\n     - Add an \"## Approaches Tried\" section before \"## How to verify it\"\n     - Include the aggregated reasoning showing failed attempts and what was learned\n     - This helps reviewers understand the journey, not just the destination\n   - Ensure all checklist items are addressed (checked or explained)\n\n8. **Save the description:**\n   - Write the completed description to `thoughts/shared/prs/{number}_description.md`\n   - Show the user the generated description\n\n9. **Update the PR:**\n   - Update the PR description directly: `gh pr edit {number} --body-file thoughts/shared/prs/{number}_description.md`\n   - Confirm the update was successful\n   - If any verification steps remain unchecked, remind the user to complete them before merging\n\n## Important notes:\n- This command works across different repositories - always read the local template\n- Be thorough but concise - descriptions should be scannable\n- Focus on the \"why\" as much as the \"what\"\n- Include any breaking changes or migration notes prominently\n- If the PR touches multiple components, organize the description accordingly\n- Always attempt to run verification commands when possible\n- Clearly communicate which verification steps need manual testing","author":"@parcadei","ownerProfile":null,"authorContacts":null,"sourceUrl":"https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/describe_pr","license":"MIT","category":"review","lang":"en","tokens":1001,"stars":0,"calls30d":1,"claimed":false,"visibility":"public","origin":"crawler","version":"0.1.0","createdAt":"2026-08-22","updatedAt":"2026-08-22","files":[],"requires":{"mcp":[],"tools":[]},"safety":{"flags":[],"scannedAt":"2026-08-22","hasScripts":false,"networkEndpoints":[]}}