br4zz4:check

Reviews code diffs, files, branches, and pull requests against project rules.

Updated May 25, 2025
One-click install
npx skills add https://github.com/oporpino/commons --skill br4zz4-check-oporpino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: br4zz4:check
Source: https://github.com/oporpino/commons/tree/main/ai/shared/skills/br4zz4%3Acheck
Command: npx skills add https://github.com/oporpino/commons --skill br4zz4-check-oporpino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ensuring every code change complies with project-specific rules and conventions is tedious and error-prone when done manually, especially across multiple languages and frameworks. ## Core Features & Use Cases - Flexible Review Scope: Review the current working diff, a specific file, a fetched branch, or a GitHub pull request by URL. - Rule-Based Evaluation: Automatically loads shared rules plus language-specific rules for Elixir, Python/Django, Ruby, React/TypeScript, Terraform, and Docker Compose based on file extensions in the diff. - Structured Findings Report: Groups violations by file with the rule violated, offending code, suggested fix, and a severity summary (blocking/warning). - Use Case: Paste a GitHub PR URL and receive a complete review of the branch diff against main, checking architecture boundaries, naming conventions, test structure, seeds, and Docker compose patterns. ## Quick Start Ask the assistant to review the current diff or a specific pull request URL against the project rules.

Frequently Asked Questions about br4zz4:check

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

FAQPage Schema
How do I review a GitHub pull request against project coding rules?▼

Pass the GitHub PR URL as the argument. The skill uses the gh CLI to fetch the PR branch, checks it out locally, computes the diff against main, and evaluates every changed file against the applicable project rules.

How to check code changes before committing?▼

Invoke the skill with no argument to review the current diff, covering both staged and unstaged changes via git diff HEAD and git diff --cached. Findings are grouped by file with rule citations and suggested fixes.

Which languages and frameworks does the rule-based review support?▼

It loads language-specific rules for Elixir, Python/Django, Ruby, React/TypeScript/JavaScript, and Terraform, plus Docker Compose checks. Files without matching rules are reviewed against shared rules and general best practices.

Can I review a single file instead of a full diff?▼

Yes, pass a file path as the argument and the skill reads that file directly, then evaluates it against the shared rules and any language-specific rules matching its extension.

What does the review report include?▼

The report groups findings by file, stating the rule violated, quoting the offending code, and suggesting a fix. It ends with a summary of issue counts across files grouped by severity as blocking or warning.