challenger

Challenges code changes, design documents, and review reports to find missed risks.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill challenger-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: challenger
Source: https://github.com/HACK-WU/skills/tree/main/skills/challenger
Command: npx skills add https://github.com/HACK-WU/skills --skill challenger-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code reviews and design reviews often conclude "no issues found" while still missing root-cause gaps, silent data loss, edge cases, and unreviewed piggyback changes. This Skill performs adversarial second-pass questioning on code changes, design documents, and analysis reports to surface risks that the first review missed. ## Core Features & Use Cases - Multi-object questioning: Applies distinct challenge strategies for bug fixes, new features, optimizations, design documents, and analysis reports produced by other skills. - Data conservation and global consistency checks: Verifies data flow, quantity, and content across consumers, traces exception handling endpoints, and re-checks the change against overall business goals and success criteria. - Piggyback change detection: Identifies unrelated "drive-by" edits in a diff and demands evidence they are safe rather than letting them ride through review. - Use Case: After a code review approves a bug fix, invoke this Skill to verify the root cause was truly fixed, callers handle the new behavior, similar functions were patched, and the fix holds under extreme conditions, producing a risk-graded challenge report. ## Quick Start Ask the AI to challenge the approved code change or design document and produce a second-pass questioning report with risk levels and improvement suggestions.

Frequently Asked Questions about challenger

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

FAQPage Schema
How do I do a second-pass review after code review approves a change?

Run an adversarial challenge pass that assumes the approval is wrong and hunts for evidence. Verify the root cause was fixed, check callers handle new behavior, search for similar unfixed patterns, and grade each finding by risk level.

What is adversarial review of design documents?

Adversarial design review assumes an approved design still has gaps and challenges goal alignment, feasibility, scenario completeness, and risk coverage. It outputs objections with reasoning chains, alternatives, and acknowledged strengths rather than a simple issue list.

How to detect silent data loss in code changes?

Apply data conservation checks: trace where modified data flows, verify quantities do not silently shrink through filters or swallowed exceptions, and confirm field content survives serialization. Every exception handler must show where the dropped data actually went.

Can this challenge reports produced by other AI review skills?

Yes, it accepts analysis or review reports from other skills as the challenge target. It focuses on caller-specified points such as whether the root cause is correct, the impact scope is complete, and the risk assessment is over- or under-stated.

When should I not rely on a single code review?

Single reviews often miss piggyback changes, cross-module impacts, and extreme-condition failures. Use a second-pass challenge when changes touch critical functionality, data pipelines, or when the first review reported no blocking issues.