arib-dev-review

Enforce an eight-gate code review process for pre-merge validation.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-dev-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arib-dev-review
Source: https://github.com/AribSudia/claude-code-methodology/tree/main/.claude/skills/arib-dev-review
Command: npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-dev-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of consistency and rigor in manual code reviews, preventing the merge of insecure, bloated, or poorly tested code into your production codebase.

Core Features & Use Cases

  • Eight-Gate Quality Enforcement: Systematically checks for function length, file size, duplication, security vulnerabilities, test coverage, and documentation.
  • Parallel Dispatch: Uses specialized subagents for security, testing, and structure to perform deep-dive analysis in parallel.
  • Use Case: Before merging a feature branch, use this skill to ensure that no hardcoded secrets exist, all new functions are documented, and test coverage is verified against both happy and edge cases.

Quick Start

Use the arib-dev-review skill to perform a comprehensive quality gate analysis on the current feature branch.

Frequently Asked Questions about arib-dev-review

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

FAQPage Schema
How do I automate pre-merge code review for feature branches?

Automated pre-merge code review enforces rigorous quality standards through an eight-gate process. It systematically checks function length, file size, duplication, security vulnerabilities, test coverage, and documentation before code reaches production.

What is an eight-gate quality enforcement process for code review?

An eight-gate quality enforcement process systematically validates function length, file size, duplication, security vulnerabilities, test coverage, and documentation. It uses parallel dispatch with specialized subagents to perform deep-dive analysis on structural integrity and maintainability.

How do I detect hardcoded secrets and security vulnerabilities during refactoring?

Security vulnerability detection during refactoring is handled by specialized subagents analyzing your codebase in parallel. This deep-dive approach identifies hardcoded secrets and enforces documentation compliance to maintain architectural integrity.

Does automated code governance work for individual file audits?

Automated code governance supports both pre-merge validation of feature branches and individual file audits. This ensures architectural integrity, vulnerability detection, and documentation compliance across professional software development workflows.

What is the best way to verify test coverage for edge cases before merging?

Verifying test coverage for edge cases is best handled through systematic quality gates that analyze both happy and edge cases. This automated validation prevents poorly tested code from merging into your production codebase.

Why does manual code review fail to prevent insecure code merges?

Manual code review lacks consistency and rigor, often allowing insecure, bloated, or poorly tested code into production. Automated quality gates enforce strict standards for security, maintainability, and test coverage to eliminate these gaps.