inquisitor

Run adversarial tests across five dimensions on a feature diff.

10|2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/raddue/crucible --skill inquisitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inquisitor
Source: https://github.com/raddue/crucible/tree/main/skills/inquisitor
Command: npx skills add https://github.com/raddue/crucible --skill inquisitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill hunts for subtle, cross-component bugs that emerge only when a full feature is assembled, preventing integration issues before they reach the final quality gate.

Core Features & Use Cases

  • 5-Dimensional Attack: Simultaneously probes for issues in wiring, integration, edge cases, state/lifecycle, and regression across the entire feature diff.
  • Automated Test Generation: Writes and runs specific adversarial tests for each identified weakness.
  • Use Case: After a complex feature involving multiple microservices and a UI update is implemented, the inquisitor skill can be run to ensure all the pieces correctly interact, state is managed across services, and no existing functionality has been broken by the new additions.

Quick Start

Run the inquisitor skill to hunt for cross-component bugs in the current feature branch.

Frequently Asked Questions about inquisitor

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

FAQPage Schema
How do I find cross-component bugs in a full feature diff?

To find cross-component bugs in a full feature diff, run an adversarial testing process that probes five dimensions: wiring, integration, edge cases, state/lifecycle, and regression. This identifies subtle integration issues before they reach the final quality gate.

What is adversarial testing for integration issues?

Adversarial testing for integration issues is a method that simultaneously attacks a feature diff across five dimensions to identify cross-component bugs. It generates and executes specific tests for each weakness to ensure components interact correctly.

Can I automatically fix bugs found during cross-component testing?

Yes, you can automatically fix bugs found during cross-component testing by enabling an optional automated fix cycle. After adversarial tests identify and execute against weaknesses, the fix cycle addresses the discovered integration and state issues.

Does adversarial testing work for complex microservice features?

Adversarial testing works for complex microservice features by probing the entire feature diff for wiring, integration, and regression issues. It ensures pieces interact correctly, state is managed across services, and existing functionality remains unbroken.

What's the best way to test state and lifecycle across multiple components?

The best way to test state and lifecycle across multiple components is a 5-dimensional adversarial test on the full feature diff. It isolates state and lifecycle issues alongside wiring and edge cases, then generates specific tests for each weakness.