defect-hunting

Enumerate data entry points and validate thresholds against reference data.

4|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/vmobifystudio/app-dev-team --skill defect-hunting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: defect-hunting
Source: https://github.com/vmobifystudio/app-dev-team/tree/main/skills/defect-hunting
Command: npx skills add https://github.com/vmobifystudio/app-dev-team --skill defect-hunting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defect hunting prevents code reviews, audits, tests, and guard rules from certifying changes that only appear correct on the visible or happy path. It exposes missed data entry points, mis-calibrated thresholds, unfailable checks, incomplete findings, and unverified claims.

Core Features & Use Cases

  • Entry-Point Auditing: Enumerate every writer and reader of persisted or user-visible data, including edit, cancel, failure, restore, import, sync, and migration paths.
  • Executable Validation: Verify thresholds, formulas, tables, rates, and other real-world claims by executing them across their full input range against independent reference data.
  • Failure-Proof Guard Rules: Ensure lint rules, CI checks, architecture tests, and shell guards can detect real violations, do not match comments, and are proven through mutation and revert testing.
  • Findings Discipline: Track every issue with a stable identifier, explicit status, evidence, and recurrence-prevention rules.
  • Use Case: Apply this skill during an app audit to discover an unvalidated edit path, prove a paywall threshold against reference cases, and verify that the new regression guard actually fails on a realistic defect.

Quick Start

Use the defect-hunting skill to audit the proposed change, enumerate all affected data paths, validate its constants and rules, and produce a finding register with evidence and explicit unchecked items.

Frequently Asked Questions about defect-hunting

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

FAQPage Schema
How do I find hidden software defects that pass code reviews and happy-path tests?

Defect hunting exposes hidden software defects by auditing all data paths, validating thresholds against reference data, and proving guard rules through mutation testing. It enumerates every reader and writer to catch issues missed by happy-path tests.

What is mutation testing and how does it verify lint rules and CI checks?

Mutation testing verifies lint rules and CI checks by introducing realistic code defects to prove the guards actually fail. It ensures checks do not match comments and can detect real violations, preventing unfailable checks from certifying bad code.

How do I validate paywall thresholds and formulas against reference data?

Executable validation verifies thresholds, formulas, tables, and rates by executing them across their full input range against independent reference data. This proves real-world claims and exposes miscalibrated constants before production deployment.

How do I audit all data entry points including cancel, restore, and sync paths?

Entry-point auditing enumerates every writer and reader of persisted data, explicitly including edit, cancel, failure, restore, import, sync, and migration paths. This exposes missed data entry points that screen-by-screen reviews fail to detect.

Does defect hunting work for tracking remediation and managing QA findings?

Yes, findings discipline tracks every issue with a stable identifier, explicit status, evidence, and recurrence-prevention rules. It produces a finding register that explicitly flags unchecked items for QA certification and remediation tracking.

Why do text-based guard rules fail to catch hidden defects in code reviews?

Text-based guard rules fail because they often match comments instead of code, cannot detect real violations, and remain unproven against mutations. Defect hunting replaces them with comment-resistant checks verified through revert testing.