review-feedback

Classifies review feedback, spreads fixes horizontally, and embeds lessons into review criteria.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Hakkadaikon/hymme --skill review-feedback-hakkadaikon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-feedback
Source: https://github.com/Hakkadaikon/hymme/tree/main/skills/review-feedback
Command: npx skills add https://github.com/Hakkadaikon/hymme --skill review-feedback-hakkadaikon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you fix only the exact spot a reviewer pointed out, the same class of mistake keeps coming back. This Skill turns every review comment or self-detected failure into a learning loop: classify why the issue escaped self-review, sweep the whole diff for similar problems, embed the new viewpoint into review criteria or hooks, and record the lesson. ## Core Features & Use Cases - Feedback Classification: Categorizes each comment as a criteria gap, missing review lens, skipped review, or detection miss, so the root cause is explicit. - Horizontal Sweep: Searches the entire diff and surrounding code with Grep/Read for the same class of problem instead of fixing one location. - Prevention Embedding: Adds the new viewpoint to diff-review lens criteria, hooks, tests, lint, or PR templates, and appends a one-line entry to tasks/lessons.md. - Use Case: After a reviewer flags a missing null check, use this Skill to find every similar unchecked call in the diff, add the pattern to the review lens criteria, and log the lesson so it never recurs. ## Quick Start Use the review-feedback skill to handle this review comment and make sure the same kind of issue is caught everywhere and prevented next time.

Frequently Asked Questions about review-feedback

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

FAQPage Schema
How do I respond to code review comments systematically?

Classify each comment by why self-review missed it, fix the pointed location, then sweep the whole diff for the same class of problem. Finally embed the viewpoint into review criteria or hooks and record a lesson so the same feedback never repeats.

How to prevent the same review feedback from repeating?

After fixing, embed the new viewpoint into a durable location such as review lens criteria files, hooks, tests, lint rules, or PR templates. Record a one-line lesson in tasks/lessons.md capturing the feedback type, root cause, and embedding target.

Does this workflow work outside formal code review?

Yes, the same loop applies to self-detected failures like red CI, root-caused bugs, or operational incidents. The classification step is reframed as why existing gates and checks failed to prevent the failure.

How does this fit with subagent-driven development fix rounds?

The implementer performs classification, horizontal sweep, and commits, writing embedding candidates in the fix report. The controller collects candidates before workspace cleanup and handles embedding and lessons, since those fall outside the task scope.

When can I skip embedding a prevention measure?

One-off feedback tied to specific code with no reproducibility can skip embedding, but that decision and its reasoning must be written in the report. Skipping silently is not allowed.