review

Review Java, Properties, YAML, SQL, and Dockerfile changes against BCE architecture rules.

1|Updated Mar 1, 2026

Search Tags:#quality assurance #code review #security #refactoring #coding standards #bce architecture

Ready to run

npx skills add https://github.com/mgoericke/claude-skills-devcontainer --skill review-mgoericke

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/mgoericke/claude-skills-devcontainer/tree/main/.claude/skills/review
Command: npx skills add https://github.com/mgoericke/claude-skills-devcontainer --skill review-mgoericke

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of reviewing code against established project conventions, architectural rules, and best practices, ensuring higher code quality and maintainability.

Core Features & Use Cases

Automated Code Analysis: Checks code against BCE architecture, lessons-learned, security, and quality standards.
Change Detection: Automatically captures staged/unstaged changes or branch diffs for review.
Structured Reporting: Provides clear findings categorized as Critical, Warning, or Note, along with positive feedback.
Fix Suggestions: Offers to correct identified issues after user confirmation.
Use Case: Before merging a new feature, run this Skill to catch potential architectural violations, security risks, or deviations from coding standards.

Quick Start

Review the code I changed in the current branch.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate code review for Spring Boot and Quarkus changes?▼

Automate code review for Spring Boot and Quarkus changes by capturing branch diffs to analyze Java, Properties, YAML, SQL, and Dockerfile formats against BCE architecture and coding standards.

What is BCE architecture and how does automated code analysis enforce it?▼

BCE architecture is a structural design pattern enforced during code review by scanning branch diffs to detect violations, categorizing findings as Critical or Warning, and suggesting fixes to maintain boundaries.

Does the code review process support analyzing YAML, SQL, and Dockerfile formats?▼

Yes, the code review process supports analyzing YAML, SQL, and Dockerfile formats, alongside Java and Properties files, to ensure security, quality, and framework-specific rules for Spring Boot and Quarkus.

How do I get structured reports with suggested fixes for security and refactoring issues?▼

Get structured reports with suggested fixes for security and refactoring issues by running automated code analysis on your branch diffs, which categorizes findings as Critical, Warning, or Note and offers corrections.

Can I review only staged and unstaged changes instead of the full branch diff?▼

Yes, you can review only staged and unstaged changes instead of the full branch diff, as the automated code analysis detects local working directory modifications to generate targeted findings and suggested fixes.