skills.rest
abranjith
abranjithCOMMUNITY
Explore all skills by this author →
GitHub

review-code

Review code changes against plan and feature specifications.

Updated Feb 15, 2026
Search Tags:#testing#architecture#code review#maintainability#pull requests#feature spec
One-click install
npx skills add https://github.com/abranjith/spec-lite --skill review-code-abranjith
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/abranjith/spec-lite/tree/main/skills/review-code
Command: npx skills add https://github.com/abranjith/spec-lite --skill review-code-abranjith

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It helps you evaluate implementation diffs against the agreed plan and feature spec so you can catch correctness, architecture, readability, testing, and performance issues before merge.

Core Features & Use Cases

  • Reviews code against memory, plan, feature, and data model context.
  • Produces prioritized findings separated into critical issues, improvements, and nitpicks.
  • Supports re-reviews after fixes and points to the correct review-report format.
  • Use case: after a feature branch is ready, you ask it to assess the changes and generate an actionable review for the team.

Quick Start

Ask the review-code skill to inspect the latest code changes against the relevant plan and feature spec and return a structured review report.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I review code changes against a feature specification before merging a pull request?▼

You can review pull requests by evaluating implementation diffs against memory rules, plan files, and feature specs to generate a structured review report with prioritized findings.

What is the best way to structure code review findings for my software engineering team?▼

The best way to structure code review findings is to separate them into prioritized categories: critical issues, improvements, and nitpicks, ensuring the team receives an actionable review report.

Can I re-review code after fixing issues on an implementation diff?▼

Yes, you can re-review code after fixes; the review process supports re-review cycles for software features and points to the correct review-report format to verify resolved issues.

Do I need plan files and feature specs to perform a maintainability code review?▼

Yes, you need memory rules, plan files, and feature specs to review code changes effectively, while optional project tools can be provided to produce prioritized findings and a structured report.

How does reviewing an implementation diff against a data model improve architecture?▼

Reviewing an implementation diff against the data model and feature context evaluates architecture and maintainability, catching structural issues and ensuring the code aligns with the agreed design plan.

Related Skills

Explore More Software Engineering Skills→
ryu-satoryu-sato

kiro-spec-requirements

Generate EARS-format requirements from feature briefs, specs, and governance rules.

Community
Advanced
indykishindykish
2

review

Analyze branch diffs against origin/main for merge safety issues.

Community
Advanced
UnicornUnicorn

analyzer-agent

Perform read-only static analysis and security scanning of codebases.

Official
Advanced
hugoduncanhugoduncan
3

clj-kondo

Lint Clojure code for syntax errors, style issues, and custom rules.

Community
Intermediate