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. Each finding contains: **file + risk** · **bad code verbatim** · **why it's wrong** · **fix with code example** - ready to paste directly into GitHub. Reviews are saved to `~/code-reviews/` for future reference. Optionally the skill then **applies** its own findings (`--fix`): fix agents edit the worktree, a read-only verifier checks each edit against the real `git diff`, static checks run, one commit lands per file, and nothing is pushed until the user says so. Procedure in `references/fix-mode.md`. No nitpicking. Critical and Important findings are reserved for things that could cause bugs, outages, data loss, security incidents, or real performance problems at scale. **HARD RULE: the `## 💰 Review Cost` block is mandatory.** Every review MUST end with a fully-populated cost block (token + price breakdown, real numbers, no `<N>` placeholders). A review without the cost block is incomplete. If you are about to present the review without it, stop and compute it first. --- ## Set up before first use This skill ships with **no** hard rules of its own: `references/house-rules.md` is a template. Fil