Review code changes via adversarial debate, reverse verification, and boundary testing.
npx skills add https://github.com/inernoro/prd_agent --skill human-verify
Please help me install this Agent Skill. Skill: human-verify Source: https://github.com/inernoro/prd_agent/tree/main/.claude/skills/human-verify Command: npx skills add https://github.com/inernoro/prd_agent --skill human-verify
Multi-perspective code verification that simulates human review. Combines adversarial debate (Devil's Advocate), reverse verification, boundary testing, and user scenario simulation to catch issues that compilers and linters miss. Trigger words: "/verify", "验证一下", "帮我检查".
Trigger the verify flow on your latest change to generate a cross-perspective validation report.
High-intent search queries and answers about installing and using this skill.
To catch edge cases missed by compilers, perform multi-perspective code review using adversarial debate, reverse verification, boundary testing, and scenario simulation. This simulates human verification to detect hidden assumptions and surface issues before merging API endpoints, UI components, or logic refactors.
Adversarial debate in code verification is a mechanism that challenges proposed changes to surface hidden assumptions. It orchestrates a Devil's Advocate perspective to simulate human review, identifying flaws in logic refactors and data processing that standard linters cannot detect.
Generate a validation report by triggering the verify flow on your latest changes. The process performs boundary testing and reverse verification, outputting a structured validation report that includes identified issues and guidance for fixes to help teams ship safer code.
Yes, multi-perspective code review works for API endpoints, UI components, data processing, and logic refactors. It validates functionality beyond surface correctness by simulating user scenarios and boundary conditions, ensuring thorough verification whenever required before merging.
The best way to validate code refactoring is using reverse verification and user-scenario simulation. By challenging the changes through adversarial review and boundary testing, you can validate functionality beyond surface correctness and generate a structured validation report.
You need scenario simulation for code verification whenever thorough validation is required before merging, especially across API endpoints, UI components, or data processing. It validates functionality beyond surface correctness by testing boundary conditions and user scenarios.
linfordWuRun static security scans, quality gates, and independent reviewer subagent before commits.
brainbrewlabsFix code scanner, security auditor, and linter issues with verified edits and reports.
MassimilianoPiliCreates JUnit 5 parameterized tests using @ValueSource, @CsvSource, and @MethodSource.
aaddrickLint shell scripts with shellcheck and GitHub Actions workflows with actionlint.
