Generate comprehensive PR descriptions following repository templates
Generates comprehensive PR descriptions by analyzing diffs, commit history, and reasoning files. Automatically runs verification tests and fills repository templates. Triggered when you ask to describe a PR or run the command.
/plugin marketplace add SiTaggart/claude-devbench/plugin install devbench@devbench-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
You are tasked with generating a comprehensive pull request description following the repository's standard template.
Read the PR description template:
.ai/thoughts/shared/pr_description.md exists.ai/thoughts/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:
.ai/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/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:
.ai/thoughts/shared/prs/{number}_description.mdUpdate the PR:
gh pr edit {number} --body-file .ai/thoughts/shared/prs/{number}_description.mdThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.