development-pr-workflow

Plugin development-pr-workflow from marketplace uniswap-ai-toolkit in Uniswap/ai-toolkit. Commands read from the repo's manifest — 12 days ago.

Skills (6)

• backtest-change

  Validate a data-driven change against LIVE historical data before it ships — replay old-vs-new over a real window, report whether it achieves its goal, and refuse to ship when the data disproves the premise. Fires whenever someone proposes a measurable change and names a number — "add a monitor at 7

• resolve-all-prs

  Resolve issues on all your open PRs in parallel. Use when user says "fix all my open PRs", "resolve issues on all my PRs", "address comments on all my pull requests", "batch fix my PRs", or "make all my PRs merge-ready".

• resolve-pr-issues

  Fix PR issues including review comments and CI failures. Use when user says "fix the failing CI on my PR", "address the review comments on PR #123", "my PR has failing checks", "help me resolve the feedback on my pull request", "the build is failing on my PR", or "make my PR merge-ready".

• review-code

  Review code changes for quality, security, and performance. Use when user says "review my changes", "do a code review", "check this for issues", "analyze code quality", "security review", "performance review", "is this PR ready", or needs architecture, security, performance, and style analysis.

• split-graphite-stack

  Split monolithic branches into logical PR stacks. Use when user says "split this branch into PRs", "break up my changes", "create a PR stack", "split stack", "make this reviewable", or has a large branch with many changes that needs to be broken into smaller, reviewable pieces.

• update-graphite-stack

  Update Graphite PR stacks by addressing review comments and syncing PRs. Use when user says "update my graphite stack", "address the review comments on my stack", "sync my PR stack after these changes", "submit my entire stack to Graphite", or "I need to update all the PRs in my stack".

Slash commands (5)

• /development-pr-workflow:backtest-change

  Backtest a data-driven change against LIVE historical data before opening the PR — replay old-vs-new and report whether it actually achieves its goal. Refuses to ship (or redirects) when the data disproves the premise. Deliberate entry point for the `backtest-change` skill.

• /development-pr-workflow:linear-task-and-pr-from-changes

  Take local changes, create a Linear task, create a branch (optionally in a worktree), commit, and publish a PR

• /development-pr-workflow:review-pr

  Orchestrate comprehensive pull request review using specialized agents for architecture, security, performance, testing, and maintainability analysis.

• /development-pr-workflow:start-linear-task

  Start working on a new Linear task by creating a worktree environment. Either provide an existing Linear ticket ID or describe the work to create a new task.

• /development-pr-workflow:work-through-pr-comments

  Methodically work through GitHub pull request comments in a conversational workflow, analyzing each comment, presenting solution options, gathering your decisions, and implementing approved changes.

Subagents (3)

• comment-resolver-agent

  Resolves PR review comments by applying code changes to specific files, handling CI failures, verifying changes locally, and reporting results

• review-executor-agent

  Executes code review tasks - addresses PR comments, fixes CI issues, and implements review feedback

• stack-splitter-agent

  Semantic analysis agent for splitting monolithic branches into logical, reviewable PR stacks. Analyzes git history, file changes, and code semantics to propose optimal split boundaries.

MCP servers (1)

• graphite

  runs: gt mcp

Similar plugins