reviews_skill

Overview

This skill discovers and triages pull request review comments, fixes critical issues aligned with PR goals, and files issues for nitpicks that are valid but out of scope. It automates fetching review threads, classifying feedback, applying fixes for critical items, and creating tracked issues for non-blocking suggestions. It integrates with the GitHub CLI and assumes the gh-pr-review extension is available.

How this skill works

The skill fetches PR context (repo slug, PR number, title/body, linked issues) to define what’s critical. It lists unresolved, non-outdated review threads, classifies each comment as CRITICAL or NITPICK, and executes handling steps. Critical comments trigger analysis, code changes, a preventive measure, a commit, and a reply; nitpicks get deduplicated, turned into issues with labels, and a reply linking the new issue.

When to use it

• A PR has unresolved review comments and you want to triage them systematically
• You need to fix feedback that directly impacts PR goals or linked issues
• You want to convert out-of-scope suggestions into tracked issues
• When enforcing team norms about who resolves threads and how to communicate changes
• Preparing a summary of review handling for teammates or release notes

Best practices

• Derive PR goals from title, body, and closing issues to decide criticality
• Always prioritize security, linked issues, PR goals, and public API breakage as critical
• Consult a review-analysis assistant before making non-trivial fixes to align with reviewer intent
• Add a systematic prevention step for each fix (linter, CI check, test, docs, or stricter typing)
• Ask the team whether you should resolve threads or wait for reviewer confirmation

Example use cases

• Fix a missing input validation pointed out in a review and add an eslint-plugin-security rule
• Convert a suggestion to refactor a helper into a tech-debt issue labeled from-review
• Respond to a documentation nitpick by creating a documentation issue and replying with the issue link
• Address a reviewer-identified breaking change by implementing the fix, committing, and notifying the thread
• Produce a concise report listing fixes applied, issues created, and prevention measures added