solution-review

Compare implemented code against task statements and generate review.md findings.

229|201|Updated May 20, 2022
One-click install
npx skills add https://github.com/blockscout/blockscout-rs --skill solution-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solution-review
Source: https://github.com/blockscout/blockscout-rs/tree/main/interchain-indexer/.cursor/skills/solution-review
Command: npx skills add https://github.com/blockscout/blockscout-rs --skill solution-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps reviewers verify that code changes faithfully implement the original task, by comparing against the task statement and artifacts and producing a structured review before handoff or merge.

Core Features & Use Cases

  • Compare implemented changes to the original task and related artifacts (task.md, solution_X.md, implementation-plan-X.md, coding-task-X.md).
  • Identify coverage gaps, regressions, and mismatches, and document evidence with file paths.
  • Generate a concise review summary (review.md) to accompany handoff or pull request.

Quick Start

Run the review workflow on the target task folder and generate a concise summary in review.md.

Frequently Asked Questions about solution-review

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

FAQPage Schema
How do I verify code changes align with the original task statement before a pull request?

Code review and diff analysis validate implemented changes against task.md and solution artifacts by detecting coverage gaps and regressions. The process generates a structured review.md artifact documenting evidence-based conclusions and recommendations for pull requests.

What is the best way to detect coverage gaps and missing acceptance criteria in code handoffs?

Detecting coverage gaps and missing acceptance criteria requires comparing implemented code against task.md and solution artifacts to find discrepancies. This enforces evidence-based findings with file paths to ensure complete task coverage before merging.

Can I generate a review summary from task.md and solution artifacts for post-implementation reviews?

Yes, you can generate a concise review summary by comparing task.md and solution artifacts during post-implementation reviews. This documents regressions and produces a final review.md artifact with conclusions for pull requests.

Does regression detection work with tmp/tasks folders containing multiple solution files?

Regression detection works by comparing task.md, solution_X.md, and related artifacts within tmp/tasks/<task-name>/ folders. It identifies mismatches between implemented code and original task statements to detect regressions across multiple solution files.

How do I document evidence-based findings with file paths during a diff analysis?

Documenting evidence-based findings during diff analysis requires comparing implemented changes against task statements and including specific file paths for every discrepancy. This generates a structured review.md artifact recording conclusions and recommendations for code reviews.