Loading...
Loading...
Found 3 Skills
Run a read-only, fresh-context branch-diff code review and report findings. Use when running /review-code, before finishing issue work, or when a local review gate should inspect committed, staged, unstaged, and untracked changes without mutating code or GitHub state.
Read-only defect review of a codebase - deep context and business-rule capture, perspective-based sweeps (business logic, error handling, security, correctness, concurrency, data integrity, performance, config, test quality), reproduction of each finding, severity calibration, and a decision-ready audit report with recommended fixes that are described but never applied. The codebase is left byte-identical. Use this whenever findings are wanted without changes, such as "review this codebase", "audit it but do not touch anything", "code review", "PR review", "second opinion on this code", "security assessment", "due diligence", "is this safe to ship", "what is wrong with this code", "review only", "report only", "read-only review", "check it without changing anything". Use it equally for business-logic defects where nothing crashes but the result is wrong - a wrong total, discount, tax or balance, a skippable step, a replayable action, a quota that does not hold, a user seeing another user's data. Prefer this over anti-bug whenever the user wants a report rather than a repaired repo, when the code belongs to someone else, or when changes need approval first. If the user actually wants the bugs fixed, use anti-bug instead.
Reviews a code change with a jury: independent read-only subagents on different models review blind, a separate judge cross-examines them and returns one verdict. Use when asked for a second opinion, a multi-model or panel review, or a high-stakes review.