skills.rest
maragudk
maragudkOFFICIAL
Explore all skills by this author →
WebsiteGitHub

address-code-review

Triage code-review comments sequentially before implementation and record decisions.

27|2|Updated Mar 27, 2026
Search Tags:#git#workflow#github#triage#code-review#pull-request#review-comments
One-click install
npx skills add https://github.com/maragudk/fabrik --skill address-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: address-code-review
Source: https://github.com/maragudk/fabrik/tree/main/skills/address-code-review
Command: npx skills add https://github.com/maragudk/fabrik --skill address-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Address Code Review helps teams methodically work through code-review feedback by walking through comments one at a time with the user. It ensures that no code changes are made until all feedback is triaged and decisions are recorded.

Core Features & Use Cases

  • Sequentially triage each review comment with the user, ensuring clarity and consensus before any changes.
  • Supports multiple sources of feedback, including review.jsonl, GitHub PRs, and in-repo documents.
  • Enforces strict phase separation: triage first, implement second, with explicit decision recording.

Quick Start

Walk through review comments one at a time, triaging each item with the user before any implementation.

Frequently Asked Questions about address-code-review

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

FAQPage Schema
How do I triage code-review feedback on GitHub pull requests?▼

You can triage code-review feedback from multiple sources including GitHub PRs, review.jsonl files, and in-repo documents. The tool processes these formats sequentially to capture every review comment for discussion.

Can I use review.jsonl files to triage code-review feedback?▼

Yes, you can triage code-review feedback directly from review.jsonl files. The tool supports review.jsonl, GitHub PRs, and in-repo documents as valid input sources for sequential comment processing.

How do I ensure code changes are not made before triaging review comments?▼

You can enforce strict phase separation by triaging all code-review feedback first and implementing changes second. This ensures no code changes occur until every review comment is discussed and decisions are explicitly recorded.

What is the best way to record decisions during a code review triage?▼

The best way to record decisions during code-review triage is to process review comments sequentially and capture the consensus for each item. This ensures every decision is documented for traceability before implementation.

Does this code-review triage process work with in-repo documents?▼

Yes, the code-review triage process works with in-repo documents. It sequentially processes feedback from in-repo documents, GitHub PRs, and review.jsonl files to ensure all comments are discussed before implementation.

Related Skills

Explore More Software Engineering Skills→
openshift-engopenshift-eng

CodeRabbit Rules from PR Reviews - Fetch Comments

Fetch and filter human PR review comments from GitHub repos into structured JSON.

Official
Intermediate
luyangliuableluyangliuable

fetch-unresolved-comments

Fetch unresolved pull request review comments from GitHub via GraphQL.

Community
Intermediate
Luney-IndustriesLuney-Industries
4

address-pr-comments

Categorize GitHub pull request comments and generate action plans.

Official
Advanced
criniscrinis
4

css-review

Reviews CSS code for redundancy, duplication, and semantic consistency with linters.

Community
Advanced