AI tools for “review”

Read-only review of Caveman Cloud evidence: cost, Cave Score, workflows, traces, latency, errors, routing, savings. Use when asked what Caveman found or where LLM spend goes.

Close out a review/meta branch that lands an evidence-ingest / curation batch: create the named nodes, ingest verified evidence, appraise Trust Magnitude, calibrate stars, wire suites, correct upstream naming, stage…

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating…

Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review…

…resumes, reports, prose. For broad requests, offers a review-focus menu (what matters most, risks/obligations, key dates & figures, or custom), classifies the document, and highlights accordingly with comments on…

Review dbt/SQL changes (models, schema.yml, sources, macros, snapshots, seeds) with altimate-code review: lineage, query equivalence, dbt anti-patterns, blast radius, PII. Prefer over generic code review when the diff…

Reviews a saved portfolio, household or model with Advisor Center analytics in three sections rendered inline in the chat — portfolio snapshot, stress scenarios, then opportunities, fund health and Funds to Explore —…

Review a Jira epic (or the Jira Product Discovery idea it implements) against its own In Scope list - which items are done, partly done, not started, or have no evidence - then flag scope conflicts and stale statuses,…

Review the last 100 calls for an agent and surface problems. Use this whenever the user wants a call-quality audit, a QA pass over recent calls, a "what's going wrong with this agent" review, or to find failed,…

Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Review code changes by collecting the review target, researching context, checking risks, and reporting findings before summary.

Review a Gaia curation PR or branch as a read-only merge gate. Use for canonical registry promotion, schema, evidence, prerequisite, nomenclature, installability, and generated-artifact checks. Route intake batches to…

Use this when reviewing AEM Edge Delivery Services (EDS, Franklin, Helix) code, either self-review at the end of development before opening a PR, or reviewing an existing pull request. Validates block structure, CSS and…

Review Zscaler Microsegmentation (ZMS) tag classification, application discovery, and tag-to-resource-group mapping. Investigates tag namespaces (CUSTOM, EXTERNAL, ML), tag keys and values, application catalog entries,…

Runs a Greptile CLI review for the current local branch, installing or authenticating the CLI when needed, then summarizes JSON findings for the user. Use when the user wants Greptile feedback before opening a PR,…

…conversions via `infa2aidp cli review generate|import`. Use after infa-migrate-mapping, before trusting any generated notebook, to surface every low-confidence conversion and REVIEW REQUIRED…

A critical, read-only quality review of one blog post or draft. Checks whether the body delivers what the title promises, the logic, every heading against its section, a technical and a marketing read, and ends with a…

…insider activity. Triggers: "does X have a moat", "moat review for X", "how durable is X's advantage", "is X's management any good", "capital allocation at X", "governance review of X", "competitive advantage of…

Preserve reasoning for independent review of plans and PRs through Qodo notes tools. Use during substantive planning and development, when decisions, scope or validation change, when resuming or handing off work, and…