bug-discovery

Probe deployed apps for software bugs after test suites pass.

7|7|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/civitas-cerebrum/element-interactions --skill bug-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-discovery
Source: https://github.com/civitas-cerebrum/element-interactions/tree/main/skills/bug-discovery
Command: npx skills add https://github.com/civitas-cerebrum/element-interactions --skill bug-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic, adversarial bug discovery after a green test suite passes, designed to uncover edge cases, performance glitches, and cross-feature issues that tests may miss.

Core Features & Use Cases

  • Phase-driven probing that starts with element probing and flow probing, then proceeds through contextual cross-references, test cross-references, context-derived analysis, classification, reproduction, and reporting.
  • Context integration with app-context.md to filter, flag discrepancies, and drive remediation prioritization.
  • Reproduction-focused outputs including test sketches and a final bug-discovery report to triage and remediate.

Quick Start

Run bug-discovery against your deployed app to begin Phase 1a element probing and start collecting findings.

Frequently Asked Questions about bug-discovery

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

FAQPage Schema
How do I find edge cases and cross-feature bugs after my Playwright test suite passes?

Adversarial bug discovery after tests systematically probes multi-page flows, boundary inputs, and race conditions to uncover hidden issues. It generates prioritized findings and reproduction steps for triage.

What is the best way to reproduce race conditions and cross-feature interaction bugs?

Adversarial probing identifies race conditions and cross-feature interactions through phase-driven element and flow testing. It produces reproduction steps and test sketches to document software bugs for triage.

How do I generate a bug-discovery report with contextual app references?

The bug discovery process integrates with app-context.md to filter findings and flag discrepancies. It cross-references tests and outputs a final bug-discovery report with reproduction steps.

Does bug discovery require screenshots for DOM-only issues?

Yes, bug discovery enforces safety by requiring screenshots for user-visible issues. DOM-only data without visual impact is explicitly surfaced as non-impact within the final QA report.

When should I use adversarial testing instead of standard QA automation?

Use adversarial testing when standard QA automation passes but you need to uncover boundary inputs and cross-feature issues. It applies contextual cross-references to probe beyond standard test coverage.