do-execute-review

Analyze git diffs and generate severity-classified code review reports.

28|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/fabio-barboza/development-orchestrator --skill do-execute-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-execute-review
Source: https://github.com/fabio-barboza/development-orchestrator/tree/main/skills/do-execute-review
Command: npx skills add https://github.com/fabio-barboza/development-orchestrator --skill do-execute-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill performs autonomous, comprehensive code reviews by analyzing git diffs, verifying conformance with project rules, validating test suites, and checking adherence to Tech Spec and Tasks. It generates a structured code review report with severity-classified findings to guide pre-merge decisions.

Core Features & Use Cases

  • Autonomous analysis of diffs and project rules to identify deviations and issues.
  • Validation against Tech Spec, PRD, and Tasks to ensure alignment.
  • Generation of a structured, severity-classified review report with actionable findings.
  • Non-intrusive: does not modify code and can be run on demand prior to QA or merge.

Quick Start

Run an autonomous review of the current branch and generate a comprehensive report.

Frequently Asked Questions about do-execute-review

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

FAQPage Schema
How do I automate code review for a git diff before merging?

Automate code review by analyzing git diffs against project rules to generate a structured report. This verifies alignment with Tech Specs and validates test suites, producing severity-classified findings for pre-merge decisions.

What is autonomous end-to-end code review and how does it work?

Autonomous end-to-end code review is a mechanism that analyzes diffs and validates conformance with project rules without modifying code. It generates an actionable, non-intrusive report of severity-classified findings to guide quality assurance.

Can I validate code against PRD and Tech Spec requirements automatically?

Yes, you can validate code against PRD and Tech Spec requirements automatically. The review process checks adherence to project tasks and specifications, ensuring alignment before generating a structured quality audit report.

Does the pre-merge code review process modify my source files?

No, the pre-merge code review process is non-intrusive and does not modify source files. It operates read-only on the git diff to produce a standalone report, making it safe to run on demand prior to QA.

What is the best way to classify code review findings by severity?

The best way to classify code review findings by severity is through an autonomous analysis of diffs and project rules. This approach generates a structured report that categorizes issues to guide pre-merge verification effectively.

When do I need an autonomous code quality audit for Git-based projects?

You need an autonomous code quality audit for Git-based projects during pre-merge verification and QA readiness. It analyzes diffs to identify deviations, ensuring your branch aligns with the PRD and Tech Spec before integration.