review-harvest

Collect merged pull request review comments into role-specific knowledge updates.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill review-harvest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-harvest
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/review-harvest
Command: npx skills add https://github.com/hirokimry/vibecorp --skill review-harvest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual burden of revisiting merged pull request review comments and turning them into durable team knowledge, rules, and documentation.

Core Features & Use Cases

  • Review harvesting: Scans merged PRs since the last run and collects replied-to review comments.
  • Role-based delegation: Routes findings to CTO, CPO, CISO, CFO, and CLO so each concern is handled by the right domain owner.
  • Knowledge persistence: Writes the distilled outcomes into a buffer worktree for later promotion into long-lived project knowledge.
  • Use case: After a busy release cycle, run this Skill to capture review lessons, avoid repeating the same mistakes, and keep organizational decisions aligned over time.

Quick Start

Ask the skill to harvest the latest merged pull request review comments and reflect them into the appropriate knowledge, rules, and documentation paths.

Frequently Asked Questions about review-harvest

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

FAQPage Schema
How do I extract knowledge from merged GitHub pull request review comments?

This Skill harvests merged GitHub pull request review comments, filtering and truncating feedback, then delegating findings to roles like CTO and CISO to generate structured knowledge updates in a buffer worktree.

What is the best way to automate post-merge code review feedback collection?

Automating post-merge code review feedback collection involves scanning merged PRs since the last run, filtering replied-to comments, and delegating them to role-specific handlers before writing updates to a buffer worktree.

Do I need GitHub CLI and jq to harvest pull request comments into a knowledge base?

Yes, GitHub CLI and jq are required dependencies for harvesting pull request comments into a knowledge base, as the Skill uses them for data retrieval, JSON parsing, and worktree locking with retry safeguards.

How does role-based delegation work for code review findings?

Role-based delegation for code review findings routes feedback to CTO, CPO, CISO, CFO, and CLO roles, ensuring each domain concern is handled by the right owner before being persisted as durable project knowledge.

Can I write harvested review comments directly to the main branch?

No, harvested review comments are written to a locked buffer worktree rather than the main branch directly, requiring a separate promotion step to integrate the distilled knowledge into long-lived project documentation.

What happens if the review harvesting process is interrupted?

If the review harvesting process is interrupted, the Skill includes delegated handling with retry and shutdown safeguards to protect the worktree state and ensure pending role-based updates are not lost.