rseng-code-reviewlisted

Covers reviewing existing code and whole projects, not just new diffs: structured codebase audits that produce ranked findings and then implement the agreed improvements, recurring project reviews after major tasks and milestones, review scoping by risk and tier, and turning review findings into tracked work and lessons. Use PROACTIVELY after major tasks and milestones, and when the user asks for a code review, codebase audit or health check of existing code, wants improvements suggested and applied, mentions reviewing the project after a milestone or before a release or submission, or when inherited or long-unreviewed code needs a structured pass. For diff-time pre-review of new work see rseng-pair-programming; for PR-time review process and rules see rseng-version-control-review.
fdiblen/rseng-agent-skills · ★ 20 · Code & Development · score 81

Install: claude install-skill fdiblen/rseng-agent-skills

# Code and project review Most review attention goes to new diffs; most risk lives in the code nobody has looked at for a year. This skill covers the retrospective forms: reviewing the EXISTING codebase with findings ranked and then implemented, and reviewing the PROJECT on a cadence - after milestones, before releases and submissions. Division of labor: rseng-pair-programming owns diff-time pre-review of new work; rseng-version-control-review owns the review process and rules; this skill owns review as an undertaking on what is already there. Review-then-implement is a two-phase contract: findings first, agreement second, changes third - never silent rewriting under the review's flag. ## The codebase review Scope before depth - review the code that matters most: 1. Map risk: recently churned complex modules (rseng-software-metrics' hotspot map), result-bearing code paths (what feeds published numbers), security surfaces (rseng-security), and anything the tests do not reach (rseng-testing's coverage). Review THOSE deeply; skim the rest. 2. Sweep with the pack's lenses, each producing findings with file:line evidence: correctness and silent-failure modes (rseng-defensive-coding), numerical practice (rseng-numerical-accuracy), design and coupling (rseng-software-design), performance red flags on hot paths (rseng-performance-profiling), hygiene and dead code (rseng-code-quality), reproducibility hazards - unseeded randomness, unpinned environ