mismagent-code-review

Reviews a block's git diff adversarially for correctness bugs, edge cases, and unsatisfied acceptance criteria.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lucolucus/mismagent --skill mismagent-code-review-lucolucus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mismagent-code-review
Source: https://github.com/lucolucus/mismagent/tree/main/codex/skills/mismagent-code-review
Command: npx skills add https://github.com/lucolucus/mismagent --skill mismagent-code-review-lucolucus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Structural verifiers confirm that tests exist and pass, but they cannot tell whether the code is actually correct or whether acceptance criteria are satisfied in spirit. This Skill performs a semantic, adversarial review of a single block's diff in a fresh-context subagent, catching logic bugs, missed edge cases, and superficially-passing tests before merge. ## Core Features & Use Cases - Three review lenses: Blind Hunter finds correctness bugs without trusting names or comments; Edge Case Hunter walks every branch, boundary, empty/error state, and concurrency path; Acceptance Auditor verifies each AC is genuinely satisfied and that discursive code rules hold. - Concurrency-claim auditing: dedicated checks that concurrency tests create real contention and that guarded operations are atomic rather than check-then-act (TOCTOU). - Finding triage and strict handoff: every finding is classified by severity (HIGH/MED/LOW) and disposition (Patch/Defer/Decision), producing a strict APPROVE/CHANGES/BLOCKED verdict consumed by the worker-composer. - Use Case: After the structural verifier passes on a block, the worker-composer dispatches this reviewer on the diff; it flags a sequential test masquerading as a concurrency test as HIGH, and the worker re-patches before merge. ## Quick Start Ask the worker-composer to run the mismagent code review on the current block's diff after the structural verifier passes.

Frequently Asked Questions about mismagent-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a semantic code review on a block diff?

The worker-composer invokes this reviewer automatically during the build movement, after the structural verifier passes. It receives the block's git diff, the block-file with its acceptance criteria, and the project's code-rules, then returns a verdict with triaged findings.

What is the difference between the verifier and the code review?

The verifier is structural and deterministic: it checks that builds and tests pass, each AC has a test, and contracts hold. The code review is semantic: it reads the actual logic to confirm tests prove the right thing and no edge case is missing.

Can the code review fix the bugs it finds?

No, it is strictly read-only. It finds and triages issues as Patch, Defer, or Decision; the worker applies Patch fixes, Defer items are recorded as future work, and Decision items require a human.

How does the review audit concurrency acceptance criteria?

It checks whether the test creates real contention with multiple threads or coroutines and a start barrier on the same instance, and whether the guarded operation is atomic rather than check-then-act. A sequential test covering a concurrency AC is flagged HIGH.

When does the code review block a merge?

It returns CHANGES when any HIGH finding exists or an AC is not truly satisfied, triggering up to two worker re-patch cycles. It returns BLOCKED when a finding requires a human decision, and APPROVE only when no HIGH findings remain.