clavix-review

Analyze git branch diffs against predefined criteria and generate structured severity reports.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/g5becks/oxlint-plugins --skill clavix-review-g5becks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clavix-review
Source: https://github.com/g5becks/oxlint-plugins/tree/main/.skills/clavix-review
Command: npx skills add https://github.com/g5becks/oxlint-plugins --skill clavix-review-g5becks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of reviewing code changes by systematically analyzing them against user-defined criteria, ensuring code quality and adherence to standards.

Core Features & Use Cases

  • Criteria-Driven Analysis: Review code based on specific dimensions like security, architecture, standards, and performance.
  • Structured Feedback: Generates detailed reports with severity levels for identified issues and positive notes.
  • Use Case: When submitting a Pull Request, use this Skill to get a comprehensive review focusing on security vulnerabilities and adherence to architectural patterns before merging.

Quick Start

Use the clavix-review skill to analyze the changes in the 'feature/new-login' branch against the main branch.

Frequently Asked Questions about clavix-review

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

FAQPage Schema
How do I automate code review for security and architecture before a pull request?

You can automate code review by analyzing git branch diffs against predefined criteria for security, architecture, standards, and performance. This Skill generates structured reports with severity levels and actionable recommendations to address vulnerabilities before merging.

Can I use git diff analysis to check code standards and performance?

Yes, git diff analysis evaluates code changes against specific dimensions including standards and performance. By retrieving branch diffs, the review process identifies deviations and generates structured feedback with severity levels to ensure adherence to coding standards.

What is criteria-driven code review and how does it evaluate branch diffs?

Criteria-driven code review systematically analyzes git branch diffs against user-specified dimensions like security and architecture. It evaluates the changes by generating a structured report that highlights identified issues with corresponding severity levels and recommendations.

How do I set up criteria-based code analysis for a feature branch?

To set up criteria-based code analysis, target your feature branch and compare it against the main branch using git. The Skill retrieves the diff and systematically analyzes the changes against security, architecture, standards, and performance criteria to produce a detailed review report.

Does this automated code review require specific dependencies or environments?

Yes, criteria-driven code review requires git installed in your environment to retrieve branch diffs. It operates independently without additional dependencies, using predefined and user-specified criteria to systematically analyze the code changes.

What is the best way to review code for security vulnerabilities and architectural patterns?

The best way to review code for vulnerabilities and patterns is using criteria-driven analysis on git branch diffs. This approach systematically evaluates changes against security and architecture dimensions, producing a structured report with severity levels and positive notes.