code-review

Automate Baan code reviews for standards, naming, and architecture.

Updated Jun 14, 2026
One-click install
npx skills add https://github.com/baan-press/baan --skill code-review-baan-press
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/baan-press/baan/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/baan-press/baan --skill code-review-baan-press

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a comprehensive code review process, ensuring that code meets Baan's standards for naming, simplicity, and maintainability.

Core Features & Use Cases

  • Code Review: Analyze code for naming honesty, simplicity, SOLID principles, DRY practices, Next.js idioms, and Baan rule compliance.
  • Scope Arguments: Review diffs, staged changes, single files, or pull requests.
  • Read-only: Never edits code, only provides a structured report.

Quick Start

Run the code-review skill on the current diff with the command: code-review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for SOLID principles and Next.js idioms?

You can automate code review by running the skill against diffs, staged changes, or pull requests to check for SOLID principles, DRY practices, and Next.js idioms. It outputs a structured report on naming honesty and architectural compliance.

What is the best way to review staged Git changes for architectural best practices?

The best way to review staged changes is using an automated code review tool that checks against defined rule definitions. This ensures adherence to coding standards and naming conventions without manually inspecting every file.

Can I use a code review script to check Baan project files without modifying my code?

Yes, you can run a read-only code review script that checks Baan project files against rule definitions without modifying code. It generates a structured report detailing naming and architectural compliance.

Does automated code review work with pull requests and single file scopes?

Yes, automated code review supports pull requests, single files, diffs, and staged changes. It evaluates the selected scope against Baan standards for simplicity, SOLID principles, and naming conventions.

What do I need to check code quality and Baan rule compliance in my project?

To check code quality and Baan rule compliance, you need access to Baan project files and rule definitions. The review process requires these to evaluate adherence to naming conventions and architectural best practices.