aidex-reviewlisted

Use when the user wants code reviewed as it stands — a module, a feature, a path, or the whole app — rather than a diff or a pull request. Covers correctness/bug hunting, simplification and dead code, exploitable security defects, and performance waste, and it first proposes which finder agents are worth launching and what they will cost. Fires on "review this module", "review the X feature", "find bugs in this module", "what dead code is in X", "can this module be simplified", "security review of this code", "review the whole app", "review the changes since Friday / this weekend" (the changes pick the modules, reviewed as they stand). Not for: reviewing a diff, branch, or PR (the built-in /code-review, /simplify and /security-review already do that); auditing a running system against Lighthouse/OWASP program methodology (aidex-audit); fixing a specific known bug (aidex-bugfix).
yacb2/aidex · ★ 2 · Code & Development · score 81

Install: claude install-skill yacb2/aidex

> **Trigger-eval probe (test-only).** As your very first action, run `printenv AIDEX_TRIGGER_EVAL_MARKER`. If it prints a non-empty path, also run `touch "${AIDEX_TRIGGER_EVAL_MARKER}.aidex-review"` before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block. # Review — code as it stands, not as it changed Every installed review instrument is anchored to a diff. `/code-review` accepts a `<path>` target but its own scope agent turns it into *"build the matching git diff command for it"*; `/simplify` reviews *"the changed code"*; `/security-review` interpolates `git diff origin/HEAD...`, an anchor that can resolve to zero files while the tree is dirty (measured 2026-07-27). This skill answers the other question: **review this module as it is**, with no base ref. Scope vocabulary for the *diff* case: `aidex-conventions/references/review-scope-conventions.md`. ## Step 1 — Resolve and measure the target (never skip) ```bash bash "${CLAUDE_SKILL_DIR}/scripts/resolve-review-target.sh" <path> # or --app ``` There is **no default target**. If the user did not name one, ask — one line — and do not fall back to the repo root. **"Review the changes" resolves to the touched modules, not to a diff.** When the ask is "review the changes since Friday / this weekend's changes / lo que cambió esta semana", run `--touched-since <ref|date>` (no path): the changes decide WHICH modules, and each owning module is measured and reviewed as it