lekker-reviewlisted

FAANG-quality PR code review, adaptable to any team. Checks out the branch in an isolated worktree, gathers context from your issue tracker, chat, docs, CI checks, and (optionally) production monitoring, runs 5 parallel specialized review agents (quality/implementation/simplification/conventions/test-quality), verifies every verdict-affecting finding against the diff, then outputs a single unified markdown review: file + risk + bad code + why it's wrong + fix, ready to paste directly into GitHub. Saves every review to ~/code-reviews/*.md. Covers business logic, scalability, complexity, data integrity, security, integration contracts, error handling, and migration safety. Critical findings come with PROOF: a prover agent writes a failing test in the worktree demonstrating each bug, and fix mode later re-runs it to show the fix flips it green. Every review also publishes a private living artifact page whose URL stays stable across re-reviews, so the author watches findings close commit by commit. With --fix (or
oleg-koval/agent-skills · ★ 3 · Code & Development · score 75

Install: claude install-skill oleg-koval/agent-skills

# Lekker Review FAANG-grade code review. Isolated worktree checkout, full context gathering (issue tracker + chat + docs + framework docs + monitoring + CI, whichever you have MCP tools configured for), then 5 parallel specialized review agents, a finding-verification pass, and one unified markdown output. An optional `--engine revmux` flag can replace the Step 2 native pipeline with revmux (profiles and lenses under `references/revmux/`). The default engine is `workflow` in Claude Code and `codex` in OpenAI Codex. All engines feed the same Step 3 synthesis and finding schema. Two modes, same review engine: | Mode | Target | Entry | |------------|-------------------------------------|-----------------------------------------| | **pr** | An open GitHub PR | a PR url / `repo N` / `repo "title"` | | **branch** | A local branch, before it is pushed | `branch [ref]`, or `--branch` | Branch mode exists to move the review left: everything a bot reviewer (Greptile, CodeRabbit, or similar) would charge for on the PR is found and FIXED locally first, so the PR opens clean and there is little left to bill for. It reviews the same diff a PR would show - merge-base against the branch the PR would target - and it defaults to `--fix`. Each finding contains: **file + risk** · **bad code verbatim** · **why it's wrong