Run blind dual adversarial code reviews with re-judging until approval or escalation.
npx skills add https://github.com/kurojs/EnderDots --skill judgment-day-kurojs
Please help me install this Agent Skill. Skill: judgment-day Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/judgment-day Command: npx skills add https://github.com/kurojs/EnderDots --skill judgment-day-kurojs
It reduces false positives and missed bugs by forcing two independent, blind adversarial judges to review the same target using the same injected standards, then only fixing confirmed findings.
Use the judgment-day skill to dual-review and re-judge a specific repository feature or pull request when you ask for “Judgment Day” or “juzgar” with the target clearly specified.
High-intent search queries and answers about installing and using this skill.
Adversarial code review reduces false positives by running blind dual judges that independently evaluate the same target. Only confirmed findings from both judges proceed to fixes, ensuring theoretical warnings are separated from real issues.
Blind dual review works by launching two parallel judges that never self-review the code and return severity-tagged findings. The confirmation workflow separates confirmed, suspect, contradiction, and informational items with explicit escalation rules.
A confirmed-only fix loop gates repairs so that only Round 1 confirmed issues are fixed. After each fix iteration, both judges re-run to re-validate the changes, ensuring strict terminal outcomes of APPROVED or ESCALATED.
Yes, dual adversarial judging applies to reviewing files, features, PRs, or architecture slices. It assesses correctness, edge cases, error handling, performance, and security against injected project standards using parallel judge execution.
When two independent judges disagree, the workflow applies explicit escalation rules. Contradictions between judges trigger strict terminal outcomes, resulting in an ESCALATED status rather than proceeding with unconfirmed fixes.
PR triage with dual reviewers normalizes severity by distinguishing real issues from theoretical warnings. The workflow categorizes findings into confirmed, suspect, contradiction, and informational items before applying confirmed-only fix gating.
NintendaDevAnalyze engine code against project rules to produce structured review reports.
SocketDevIteratively scan, fix, and re-scan code until quality findings reach zero.
swarm-ai-researchGenerate severity-tagged findings, inline comments, and verdicts for pull requests.
naviktSet up Rust projects with cargo, linting, and async templates.
