review

Review Verona compiler code changes against project guidelines and tests.

6|4|Updated Apr 9, 2025
One-click install
npx skills add https://github.com/sylvanc/verona-bc --skill review-sylvanc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/sylvanc/verona-bc/tree/main/.claude/skills/review
Command: npx skills add https://github.com/sylvanc/verona-bc --skill review-sylvanc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured, principle-driven code review process to ensure code quality, adherence to project conventions, and architectural integrity for the Verona compiler.

Core Features & Use Cases

  • Automated Build & Test: Checks if the code compiles and passes tests.
  • Principle Compliance: Evaluates code against established C++ style, Trieste Patterns, Architecture, Testing & Robustness, and Verona Style guidelines.
  • Use Case: Use this Skill after implementing a new feature to catch potential issues and ensure the code aligns with project standards before merging.

Quick Start

Use the review skill to perform a code review on 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 perform a principle-based code review for the Verona compiler?

To perform a principle-based code review for the Verona compiler, this Skill analyzes your current branch's git diff against C++ style, Trieste Patterns, architectural guidelines, testing conventions, and Verona-specific idioms to ensure software quality.

What coding standards are checked during an automated Verona compiler code review?

An automated Verona compiler code review checks general correctness, C++ style, Trieste Patterns, architectural guidelines, testing conventions, and robustness, alongside specific Verona coding idioms to maintain software quality.

Do I need git to run an automated code review on my C++ compiler project?

Yes, you need git installed to run this automated code review, because the Skill requires git for diffing code changes and verifying build and test commands against the established principles.

When should I use an automated code review for my C++ compiler project?

You should use an automated code review after implementing a new feature or code changes to catch potential issues, verify that the code compiles and passes tests, and ensure alignment with project standards before merging.

What is the best way to verify code compliance with Trieste Patterns before merging?

The best way to verify code compliance with Trieste Patterns before merging is to execute a principle-based review that evaluates your code changes against the project's established architectural and testing conventions.

Can this code review verify that my C++ code compiles and passes tests automatically?

Yes, this code review can verify that your C++ code compiles and passes tests automatically by executing required build and test commands during its principle-based analysis of your current branch.