devflow-review

Name: devflow-review
Availability: InStock
Author: abdias98

Analyze code diffs against architecture specs and engineering standards.

1|Updated Mar 30, 2026

Search Tags:#automation #testing #architecture #security #standards #code-review #diff-analysis

Ready to run

npx skills add https://github.com/abdias98/DevFlow --skill devflow-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devflow-review
Source: https://github.com/abdias98/DevFlow/tree/main/.agents/skills/devflow-reviewer
Command: npx skills add https://github.com/abdias98/DevFlow --skill devflow-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates thorough code reviews by analyzing diffs against architecture specifications and development plans (cycle mode) or directly against engineering standards (standalone mode), helping teams identify issues early and improve quality without manual review fatigue.

Core Features & Use Cases

Automated diff-driven code review against architecture specs and plan in cycle mode.
Standalone mode for engineering-standards based review across backend/frontend changes.
Classifies findings as BLOCK, WARN, or INFO and routes blockers back to the Implementer.
Supports targeted reviews via optional file path inputs and review of all changes.

Quick Start

Provide diffs or specify files to review and invoke the reviewer in cycle or standalone mode to begin.

Frequently Asked Questions about devflow-review

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

FAQPage Schema

How do I automate code review against architecture specifications?▼

Automated code review against architecture specs is performed by analyzing diffs alongside development plans in cycle mode, enforcing reference documents and routing blockers back to the implementer. It classifies findings into BLOCK, WARN, or INFO categories.

What is diff analysis in automated code review?▼

Diff analysis in automated code review is the process of evaluating code changes against predefined engineering standards, architecture specifications, or development plans to identify security, performance, and test coverage issues early.

Can I review specific file paths for security and performance issues?▼

Yes, you can perform targeted reviews of specific file paths for security and performance issues by providing optional file path inputs. This allows reviewing all changes or focusing on specific backend or frontend files.

How do I classify code review findings as blockers or warnings?▼

Code review findings are automatically classified into BLOCK, WARN, and INFO categories based on their severity against engineering standards and architecture specs, with identified blockers routed directly back to the implementer for resolution.

What is the best way to review code changes without manual review fatigue?▼

Automating diff-driven code review eliminates manual review fatigue by evaluating changes against architecture specs in cycle mode or engineering standards in standalone mode, ensuring consistent quality and early issue detection.

Does standalone code review work for both backend and frontend changes?▼

Yes, standalone mode supports engineering-standards based review across both backend and frontend changes, analyzing diffs to enforce criteria and generate per-file findings without requiring architecture specifications.