review-implementing
starsforks
How to install review-implementing?
omnigentx/jarvis/review-implementing
$npx -y skills add omnigentx/jarvis --skill review-implementingProcess and implement code review feedback systematically. Use when receiving review comments or FAIL verdicts and needing to address them.
SKILL.md
| 1 | # Implementing Review Feedback |
| 2 | |
| 3 | Adapted from [mhattingpete/claude-skills-marketplace](https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/review-implementing). |
| 4 | |
| 5 | ## When to Use |
| 6 | |
| 7 | - After receiving a FAIL verdict in a meeting |
| 8 | - When reviewer lists issues to address |
| 9 | - When code review comments need to be implemented |
| 10 | |
| 11 | ## Systematic Workflow |
| 12 | |
| 13 | ### 1. Parse Feedback |
| 14 | - Extract individual issues from the review |
| 15 | - Categorize: Critical → Important → Minor |
| 16 | - Clarify ambiguous items before starting |
| 17 | |
| 18 | ### 2. Prioritize |
| 19 | Fix in order: |
| 20 | 1. **Critical** — Must fix before anything else |
| 21 | 2. **Important** — Fix before requesting re-review |
| 22 | 3. **Minor** — Fix if time permits, or note for later |
| 23 | |
| 24 | ### 3. Fix Each Issue |
| 25 | For each item: |
| 26 | 1. **Locate** the relevant code |
| 27 | 2. **Understand** the reviewer's intent |
| 28 | 3. **Make the change** — minimal, focused fix |
| 29 | 4. **Verify** — check syntax, run relevant tests |
| 30 | 5. **Report** — show what you changed in your `speak()` |
| 31 | |
| 32 | ### 4. Request Re-Review |
| 33 | After fixing Critical and Important issues: |
| 34 | - Summarize what you fixed |
| 35 | - Show test results |
| 36 | - Ask reviewer to re-check |
| 37 | |
| 38 | ## Handling Edge Cases |
| 39 | |
| 40 | **Conflicting feedback:** |
| 41 | - Ask PM for guidance in the meeting |
| 42 | |
| 43 | **Breaking changes required:** |
| 44 | - Notify team before implementing |
| 45 | |
| 46 | **Tests fail after fix:** |
| 47 | - Fix tests before reporting done |
| 48 | |
| 49 | **Can't reproduce the issue:** |
| 50 | - Ask reviewer for more details |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
