Skip to main content

Overview

The AIOX Quality Gate System provides automated quality assurance through three progressive layers of validation. Each layer catches different types of issues at the appropriate stage of development.

The 3-Layer Architecture

Layer 1: Pre-commit Checks

Purpose

Fast, local checks that run before code is committed. Catches obvious issues immediately.

Checks Included

Configuration

Running Layer 1

Expected Output

Layer 2: PR Automation

Purpose

AI-assisted code review that runs on pull requests. Catches deeper issues like logic errors, security vulnerabilities, and architectural problems.

Tools Integrated

Severity Levels

Configuration

Running Layer 2

CodeRabbit Integration

CodeRabbit performs AI-powered code review with these focus areas:
  • Security vulnerabilities
  • Performance issues
  • Code quality and maintainability
  • Best practices violations
  • Documentation completeness

Quinn (@qa) Integration

The QA agent performs automated review focused on:
  • Test coverage adequacy
  • Edge case handling
  • Error handling completeness
  • Acceptance criteria validation

Layer 3: Human Review

Purpose

Strategic human review for final sign-off. Ensures business requirements are met and architectural decisions are sound.

Configuration

Review Checklist

Sign-off Process

CLI Commands

aiox qa run

Run quality gate checks.

aiox qa status

Check current quality gate status.
Output:

aiox qa report

Generate quality gate report.

aiox qa configure

Configure quality gate settings.

CI/CD Integration

GitHub Actions

Pre-commit Hook

Troubleshooting

Layer 1 Failures

Layer 2 Failures

Layer 3 Issues

Best Practices

Layer 1

  1. Run locally before commit - Don’t wait for pre-commit hook
  2. Fix issues immediately - Don’t accumulate technical debt
  3. Keep tests fast - Optimize slow tests
  4. Use caching - Leverage .eslintcache and .tsbuildinfo

Layer 2

  1. Address critical issues first - They block the merge
  2. Document medium issues - Create follow-up stories
  3. Review Quinn feedback - AI catches patterns you might miss
  4. Keep PRs small - Easier to review, faster CI

Layer 3

  1. Complete checklist thoroughly - Each item has a purpose
  2. Ask questions - Don’t approve what you don’t understand
  3. Consider long-term impact - Not just immediate functionality
  4. Provide constructive feedback - Help improve code quality

Performance Optimization

Layer 1 Speed

  • First run: ~10-15s (no cache)
  • Subsequent runs: Less than 5s (cached)
  • Optimization: Clear caches if corrupted

Layer 2 Speed

  • CodeRabbit: 2-5 minutes typical
  • Quinn: 1-3 minutes typical
  • Optimization: Run in parallel when possible

Layer 3 Speed

  • Human review: Variable (hours to days)
  • Optimization: Clear checklist, good PR description