analysis-review

Convert code review results into prioritized action plans by severity.

3|2|Updated Jun 13, 2025
One-click install
npx skills add https://github.com/poteto-go/go-alchemy-sdk --skill analysis-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analysis-review
Source: https://github.com/poteto-go/go-alchemy-sdk/tree/main/.gemini/skills/analysis-review
Command: npx skills add https://github.com/poteto-go/go-alchemy-sdk --skill analysis-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After receiving a code review result, this skill builds an actionable plan to fix issues. It enforces that an action plan is mandatory when the score is 95 or below.

Core Features & Use Cases

  • Generate a prioritized action plan by severity to address the highest deductions first.
  • Ignore typos and focus on substantive fixes to maximize score recovery.
  • Stop when the projected score exceeds 95, delivering a complete plan for release-quality improvements.

Quick Start

Generate an action plan from a code review result to reach a final score above 95.

Frequently Asked Questions about analysis-review

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

FAQPage Schema
How do I turn code review results into an action plan for fixes?

To turn code review results into an action plan, this skill applies a deterministic rule set to map deductions into concrete tasks, prioritizing fixes by severity to maximize score recovery.

What is the best way to prioritize code review deductions for software engineering?

The best way to prioritize code review deductions is by severity, addressing the highest deductions first. This skill enforces prioritization to ensure substantial quality improvement.

Does the action plan stop generating tasks if my code review score exceeds 95?

Yes, the action plan stops generating tasks when the projected score exceeds 95. An action plan is mandatory only when the initial review score is 95 or below.

How do I handle typos and minor issues when creating a code review action plan?

When creating a code review action plan, this skill automatically ignores typos and minor issues to focus on substantive fixes. This approach maximizes score recovery efficiently.

Can I use this for any code base and review scenario to improve quality?

Yes, you can use this for any code base and review scenario to improve quality. It covers typical code bases by applying a deterministic rule set that maps deductions to concrete tasks.