skills.rest
leocosta
leocostaCOMMUNITY
Explore all skills by this author →
𝕏@leoccostaGitHub

respond-to-review

Verify PR review comments against code and complete the post-fix loop.

4|Updated Mar 21, 2026
Search Tags:#automation#workflow#code-review#rules#pr-review#thread-management
One-click install
npx skills add https://github.com/leocosta/octopus --skill respond-to-review-leocosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: respond-to-review
Source: https://github.com/leocosta/octopus/tree/main/skills/respond-to-review
Command: npx skills add https://github.com/leocosta/octopus --skill respond-to-review-leocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Process PR feedback comments by verifying critiques against the code, asking for evidence on generic comments, and ensuring changes are reasoned rather than performative.

Core Features & Use Cases

  • Five-rule protocol guides responses to reviewer comments with clear decision criteria.
  • Post-fix loop consolidates edits into a single commit, conditional push, inline replies, and thread resolution for closure.
  • Seamless integration with /octopus:pr-comments to drive end-to-end PR feedback workflows.

Quick Start

Invoke the respond-to-review workflow on a PR thread to apply the five rules and complete the post-fix loop end-to-end.

Frequently Asked Questions about respond-to-review

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

FAQPage Schema
How do I automate responses to code review comments on GitHub PRs?▼

Automate code review responses by applying a five-rule protocol that verifies reviewer critiques against the codebase, then completes a post-fix loop with commits, pushes, inline replies, and thread resolution.

What is the best way to manage PR review threads and ensure changes are evidence-based?▼

Manage PR review threads by using a five-rule protocol that requests evidence for generic comments and verifies critiques against the code, ensuring changes are reasoned rather than performative.

How do I close the feedback loop after fixing code in a PR review thread?▼

Close the PR feedback loop by consolidating edits into a single commit, conditionally pushing changes, posting inline replies to reviewer comments, and resolving the thread.

Can I integrate PR comment workflows with thread management for end-to-end review processing?▼

Yes, the workflow integrates with PR comment commands to drive end-to-end feedback processing, covering explicit comments, threaded discussions, and complete post-fix closure.

Why should I verify reviewer critiques against the code before making PR changes?▼

Verifying critiques against the code prevents performative changes by ensuring every edit is evidence-based, requiring proof for generic comments and applying clear decision criteria.

Does this PR feedback workflow require any external dependencies to run?▼

No external dependencies are required to run the PR feedback workflow, as it operates independently to process comments and guide safe, evidence-based code changes.

Related Skills

Explore More Software Engineering Skills→
kylesnowschwartzkylesnowschwartz
105

sc-pull-request-skills

Fetch and resolve GitHub PR review threads via Bash scripts and APIs.

Community
Advanced
Leep-GHLeep-GH

pr-review-response

Generate per-comment PR review replies with traceable commit links.

Community
Advanced
kryota-devkryota-dev
1

pr-review

Automate PR code reviews via GitHub MCP Server with inline comments.

Community
Advanced
ohyesgocoolohyesgocool

address-review

Triage and resolve code-review feedback on merge requests.

Community
Advanced