address-pr-feedback
Address PR Feedback
Fetch all review comments on a pull request, categorize them, fix what should be fixed using TDD, and summarize the results.
Step 1: Identify the Pull Request
Determine which PR to work on using this priority order:
$ARGUMENTSprovided — If the user passed a PR number or URL, use it directly:- A number like
42→gh pr view 42 - A URL like
https://github.com/owner/repo/pull/42→ extract the number and use it
- A number like
- Current branch has a PR — Run
gh pr view --json number,url,title,stateto detect a PR for the current branch - Ask the user — If neither works, ask: "I couldn't detect a PR for the current branch. Please provide a PR number or URL."
Validate that the PR is in an OPEN state. If it is merged or closed, inform the user and stop.
Store the PR number, URL, repo owner, and repo name for later steps. Extract owner and repo with:
More from queso/ai-team-skills
write-prd
Creates a new Product Requirements Document (PRD) with auto-numbered filenames in the project's PRD directory. Runs a mini-discovery workshop to gather context, then produces a structured PRD scaled to the feature's complexity.
13v0-setup
Fetches v0.dev designs via the Platform API and prepares them for adaptation into your project. Handles folder setup, source code retrieval, component inventory, and produces an adaptation brief. Use when integrating v0 designs.
12start-new-app
Scaffolds a new app from the context-kit template. Clones the repo, renames the project, initializes git, creates a PRD directory, and asks the user to provide a PRD.
8code-review
Reviews all unmerged code in the current branch for readability, security, correctness, types, and test quality. Produces a summary of issues to fix before merging.
1