Generate comprehensive PR descriptions following repository templates
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/describe_pr/SKILL.mdYou are tasked with generating a comprehensive pull request description following the repository's standard template.
Read the PR description template:
thoughts/shared/pr_description.md existsthoughts/shared/pr_description.mdIdentify the PR to describe:
gh pr view --json url,number,title,state 2>/dev/nullgh pr list --limit 10 --json number,title,headRefName,authorCheck for existing description:
thoughts/shared/prs/{number}_description.md already existsGather comprehensive PR information:
gh pr diff {number}gh repo set-default and select the appropriate repositorygh pr view {number} --json commitsgh pr view {number} --json baseRefNamegh pr view {number} --json url,title,number,state4b. Gather reasoning history (if available):
ls .git/claude/commits/*/reasoning.md 2>/dev/nullbash "$CLAUDE_PROJECT_DIR/.claude/scripts/aggregate-reasoning.sh" mainAnalyze the changes thoroughly: (ultrathink about the code changes, their architectural implications, and potential impacts)
Handle verification requirements:
make check test, npm test, etc.), run it- [x]- [ ] with explanationGenerate the description:
Save the description:
thoughts/shared/prs/{number}_description.mdUpdate the PR:
gh pr edit {number} --body-file thoughts/shared/prs/{number}_description.mdparcadei/Continuous-Claude-v3
d07ff4b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.