Adversarial verification — three competing agents (issue-finder, disprover, judge). Triggers "verify", "double check", "are you sure", "poke holes"; pre-prod, post-critical-fix.
How to install verify?
darkroomengineering/cc-settings/verify
$npx -y skills add darkroomengineering/cc-settings --skill verifyInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/darkroomengineering/cc-settings" --skill "darkroomengineering/cc-settings/verify"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/darkroomengineering/cc-settings" that are relevant to the current task. Run `npx skills add "https://github.com/darkroomengineering/cc-settings"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- tddTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.Jul 2026
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeJul 2026
- qaInteractive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues.Jul 2026
- verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output…Jul 2026
- webapp-testingToolkit for interacting with and testing local web applications using Playwright.Jul 2026
- playwright-best-practicesUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking…Jul 2026
