feature-review

Review feature branch changes against base branch and feature specifications.

1|Updated Mar 2, 2026

Search Tags:#git #testing #quality assurance #code review #CI/CD #feature branch

Ready to run

npx skills add https://github.com/sjev/robodev --skill feature-review-sjev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-review
Source: https://github.com/sjev/robodev/tree/main/skills/feature-review
Command: npx skills add https://github.com/sjev/robodev --skill feature-review-sjev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes made on a feature branch against the original feature specification, ensuring quality and adherence to requirements before merging.

Core Features & Use Cases

Automated Code Review: Compares committed changes on a feature branch against the main branch.
Spec Compliance Check: Verifies that acceptance criteria and test plans from the feature spec are met.
Issue Identification: Surfaces critical and suggestion-level improvements in code quality, completeness, and test coverage.
Use Case: After implementing a new user authentication flow, run this skill to get a detailed report on whether the code meets the defined acceptance criteria and if all tests are passing.

Quick Start

Run the feature-review skill to review the 'auth-login' feature branch.

Frequently Asked Questions about feature-review

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

FAQPage Schema

How do I automate code review for a git feature branch against a base branch?▼

Automated code review for a git feature branch compares committed changes against a base branch, evaluating completeness, test coverage, code quality, and potential bugs. It generates a review report and updates the feature spec status to ensure quality before merging.

How does spec compliance checking work during a feature branch review?▼

Spec compliance checking verifies that committed code changes meet the acceptance criteria and test plans defined in the feature specification. It identifies completeness issues and surfaces suggestion-level improvements to ensure the implementation matches requirements.

Can I check test coverage and code quality before merging a feature branch?▼

You can check test coverage and code quality by reviewing committed changes on a feature branch. The process identifies critical issues and suggestion-level improvements in completeness, generating a detailed report on whether defined acceptance criteria are met.

What is the best way to verify feature spec compliance in a CI/CD pipeline?▼

Verifying feature spec compliance in a CI/CD pipeline involves evaluating committed changes against feature specifications and test plans. This automated review identifies potential bugs and test coverage gaps, outputting a review report and updating the feature spec status.

Do I need a feature specification to review code changes on a feature branch?▼

A feature specification is needed to review code changes effectively, as the process evaluates committed changes against defined acceptance criteria and test plans. Without the spec, the review cannot verify completeness or update the feature spec status.

Why does my feature branch review report missing test coverage and code quality issues?▼

A feature branch review reports missing test coverage and code quality issues because it evaluates committed changes against feature specifications and test plans. It surfaces critical bugs and suggestion-level improvements to ensure completeness before merging.