code-review-incorporate

Automates applying code-review feedback and updating disposition tables with commits and trailers.

157|12|Updated Feb 2, 2026

Search Tags:#automation #git #code-review #development-process #bead #disposition-table

Ready to run

npx skills add https://github.com/dcosson/h2 --skill code-review-incorporate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-incorporate
Source: https://github.com/dcosson/h2/tree/main/internal/config/templates/styles/opinionated/skills/code-review-incorporate
Command: npx skills add https://github.com/dcosson/h2 --skill code-review-incorporate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating reviewer feedback into concrete code changes, updating disposition tables, and coordinating follow-up reviews is error-prone and slow.

Core Features & Use Cases

Automatically translate findings from a review doc into code edits and structured commits with review trailers.
Update the disposition table and track progress across multiple findings and review rounds.
Coordinate end-to-end review workflows using bead IDs, review documents, and trailers for traceability.

Quick Start

Provide the path to the review document to begin the incorporation workflow.

Frequently Asked Questions about code-review-incorporate

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

FAQPage Schema

How do I automate applying code-review feedback to my git commits?▼

You can automate code-review feedback by translating findings from a review document into code edits and structured commits with review trailers. This workflow updates the disposition table and tracks progress across multiple findings and review rounds using bead IDs.

What is a disposition table in a structured code-review workflow?▼

A disposition table in a code-review workflow tracks the resolution status of individual findings across commits. It coordinates end-to-end review rounds by linking bead IDs, review documents, and commit trailers for full traceability.

How do I start incorporating code review findings using a review document?▼

To start incorporating code-review findings, provide the path to the review document to begin the incorporation workflow. The system then translates findings into code edits and generates commits with the appropriate review trailers.

Can I track multiple rounds of code review findings in a single development process?▼

Yes, you can track multiple rounds of code-review findings in a single development process. The workflow updates the disposition table and tracks progress across individual findings, coordinating follow-up reviews using bead IDs and commit trailers.

Does this code review automation support staged workflows with integration hooks?▼

Yes, the code-review automation supports staged workflows with integration hooks. It generates commits with trailers, updates review documents, and tracks dispositions for individual findings across structured review rounds.

What is the best way to maintain traceability when translating reviewer feedback into code changes?▼

The best way to maintain traceability is using bead IDs, review documents, and commit trailers to coordinate the end-to-end workflow. This method automatically translates findings into code edits while updating the disposition table across review rounds.