pr-followup

Automating pull request follow-ups involves fetching PR discussion threads via the GitHub API, analyzing developer responses to review comments, and generating a structured resolution report to determine if concerns were resolved. The Skill evaluates replies and produces a reproducible decision tree with recommended actions.

Discussion tracking for GitHub pull requests works by fetching detailed comment threads and replies using gh pr view or gh api commands. It analyzes each developer response to determine whether changes were made or valid reasoning was provided, producing a structured resolution report for audit trails and team handoffs.

Yes, you can use gh api to fetch PR comments and replies for evaluating developer responses. The Skill requires GitHub API integration via gh pr view or gh api to read discussion details, analyze responses, and output a reproducible decision tree determining whether issues were addressed.

The best way to track PR review comment resolutions is to fetch all discussion details via the GitHub API, analyze each developer response for changes or valid reasoning, and produce a structured resolution report with recommended actions. This ensures reproducible decision tracking for audit trails and team handoffs.

Yes, you need to provide the PR URL and discussion URLs to initiate the automated follow-up review. The Skill uses these inputs to fetch discussion details via GitHub API integration and evaluate whether developer responses adequately addressed the original review concerns.

Automating PR feedback follow-ups is limited to PRs with accessible discussion threads fetched via gh pr view or gh api. It requires valid PR and discussion URLs to function, and produces a structured resolution report based on analyzing developer responses rather than directly modifying the codebase.