reviewlisted

# Review Changes Run all applicable validators against recent changes and report findings. **Step 2 (rule injection) runs before validation.** If no project rules are found, validation continues with validator built-in rulesets. Run `/setup-project` to configure project-specific rules. ## Step 1: Identify what changed Get changed files. Combine committed, staged, and unstaged changes to capture all recent work: ```bash { git diff HEAD~1 HEAD --name-only --diff-filter=ACMRT 2>/dev/null; git diff --cached --name-only --diff-filter=ACMRT 2>/dev/null; git diff --name-only --diff-filter=ACMRT 2>/dev/null; } | sort -u ``` The `--diff-filter=ACMRT` includes Added, Copied, Modified, Renamed, Type-changed (excludes Deleted). Collect the list of changed files and their directories. ## Step 2: Inject applicable rules Collect project rules from the project's rule directory. Rule file locations vary by agent platform: - Claude Code: `.claude/rules/*.md` - OpenCode: `AGENTS.md` (auto-loaded natively) - Other agents: check agent documentation for project rule conventions For Claude Code, use the Glob tool to discover `.claude/rules/*.md` files, then the Read tool to load them. OpenCode auto-loads rules from `AGENTS.md` at the platform level. **Path-scoped filtering:** Always include universal and local-supplements rule files. For files with `paths:` frontmatter, include only if at least one declared path pattern matches a changed file from Step 1. Files without `paths:` frontmatt