respond

Score GitHub PR comments and CI status to prioritize fix, ask, or pushback actions.

2|Updated Sep 12, 2016

Search Tags:#automation #github #triage #code-review #pull-request #pr-review #ci-checks

Ready to run

npx skills add https://github.com/paulnsorensen/dotfiles --skill respond-paulnsorensen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: respond
Source: https://github.com/paulnsorensen/dotfiles/tree/main/claude/skills/respond
Command: npx skills add https://github.com/paulnsorensen/dotfiles --skill respond-paulnsorensen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews can become a bottleneck due to scattered comments, blocking CI failures, and unclear guidance. This Skill automatically triages review feedback by reading CI status and mergeability, scoring each inline thread and PR-level comment, and surfacing high-priority actions to accelerate the review process.

Core Features & Use Cases

Scores each unresolved inline thread and PR-level comment to determine actionable items.
Checks PR health (CI status and mergeability) before applying changes to avoid wasted effort.
Generates a clear triage table with actions (FIX, ASK, PUSH BACK) and applies inline or review-body updates.
Ideal for teams using GitHub PR workflows seeking faster, more deterministic review cycles and better decision-making.

Quick Start

Say "respond to PR comments" to begin triage on the current pull request.

Frequently Asked Questions about respond

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I triage GitHub pull request review comments automatically?▼

You can triage GitHub pull request review comments automatically by scoring each inline thread and PR-level comment to decide immediate fixes, pushbacks, or requests for input. This process checks CI status and mergeability before applying changes to maintain review flow.

What is the best way to prioritize actions on a PR with failing CI checks and unresolved threads?▼

Prioritizing PR actions involves checking CI status and mergeability first to avoid wasted effort, then scoring unresolved inline threads to generate a triage table. This table surface high-priority actions like FIX, ASK, or PUSH BACK to accelerate the review cycle.

How do I decide whether to fix or push back on code review feedback?▼

Deciding whether to fix or push back on code review feedback uses a 4-step scoring framework that evaluates each inline thread and PR-level comment. This framework outputs concrete actions to either resolve the comment, request user input, or push back.

Can I automate GitHub PR triage without losing track of unresolved discussion threads?▼

Yes, you can automate GitHub PR triage while tracking unresolved discussions using a resumable triage table. This table records the status of each inline thread and PR-level comment so you can pause and resume the review process without losing context.

How does automated PR triage handle mergeability and CI status before applying updates?▼

Automated PR triage checks PR health by reading CI status and mergeability before applying any inline or review-body updates. This ensures changes are only made when the pull request is ready, preventing wasted effort on blocked code.