review
/review # review current branch vs main
/review my-feature-branch # review a specific branch vs main
Spawns dedicated Breaker (correctness) and API Analyst (compatibility/conventions) sub-agents in parallel while the orchestrator performs the Inspector pass (architecture, tests, performance, security). Depth is user-selected.
Optimize for high-confidence, concise findings. Silence is better than speculation.
Input
Target: $ARGUMENTS
Parse $ARGUMENTS:
- Review target (positional argument):
- Non-empty text (e.g.,
my-feature-branch) -> diff that branch vs main - Empty -> diff current branch vs main
- Non-empty text (e.g.,
Step 1: Confirm Mode
More from microsoft/fluidframework
fluid-pr
Use when creating a pull request in the Fluid Framework repo. Composes a PR title and body following Fluid Framework conventions, proposes them to the user, then pushes the branch and creates the PR on GitHub. Triggers on "create a PR", "make a PR", "open a PR", "submit a PR", or "push and create a PR".
2api-changes
Use when customer-facing API changes were made — i.e., API report .md files differ from main. Guides through release tag assignment, API Council review requirements, breaking change classification, deprecation process, and changeset guidance. Triggered automatically by ci-readiness-check when api-report diffs are detected.
2fluid-pr-guide
Use when composing, writing, drafting, or reviewing a PR title, PR description, or PR body in Fluid Framework — provides title style, body template, and section guidance.
2ci-readiness-check
Use when the user explicitly asks for a CI check or to push their branch — e.g. "ci readiness", "check ci", "pre-push check", "ready for CI", "ci check", "ready to push", "push my changes", "push the branch", "let's push". Catches common CI failures before pushing — formatting, stale API reports, missing changesets, policy violations.
2