Quality

PR Review systematically reviews pull requests for code quality, security, performance, and architecture using prioritized comment templates and constructive feedback.

Refactor performs safe, incremental code refactoring with quantitative SOLID principles evaluation, visualizing technical debt and clarifying improvement priorities.

Audit Library Health runs validation, doctor, and sync checks on a skills library so it is consistent and ready to share. Use before pushing a library to a shared repo.

Skill Review evaluates whether a skill belongs in a library by previewing content, checking frontmatter, validating structure, and deciding to keep, curate, or remove. Use it when auditing a skill catalog or before adding a new skill.

AntiVibe analyzes any codebase—new, legacy, or AI-generated—and produces educational explanations or architectural audits. Use it when you want to understand the what and why behind code, rather than just accepting it.

CLI Review runs a Greptile code review from the current local git branch, installing or authenticating the Greptile CLI if needed, and then summarizes the JSON findings for actionable next steps.

Code Review Reception helps you evaluate code review feedback before making changes. Use it when comments are unclear, risky, disputed, or may conflict with the codebase or prior decisions.

Codex Advisor gets a focused second opinion from GPT through the Codex CLI, without handing work over. Use it when you need a cross-model review, a plan check before committing, or another view after repeated failures.

Requesting Code Review dispatches a reviewer subagent with a focused evidence pack instead of your session history. Use it after implementation slices, before merges, or when you need an independent review of risks and compatibility.

Review PR finds bugs, regressions, missing tests, and risky changes in a pull request. Use it when you need a focused review of only the changed code.

Systematic Debugging helps diagnose bugs, test failures, and unexpected behavior before proposing fixes. It guides isolation, root-cause tracing, owner identification, and minimal verification at the canonical owner.

Test-Driven Development defines when to use strict TDD and how to run RED/GREEN/REFACTOR with Aegis. Use it for explicit test-first work, bug fixes, and behavior changes that need failing tests before code.