epic-scan

Scan refactoring approaches for hidden gaps, regressions, and DNA violations.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/antigravityos187-sketch/universal-or-strategy --skill epic-scan-antigravityos187-sketch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-scan
Source: https://github.com/antigravityos187-sketch/universal-or-strategy/tree/main/.bob/skills/epic-scan
Command: npx skills add https://github.com/antigravityos187-sketch/universal-or-strategy --skill epic-scan-antigravityos187-sketch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jcodemunch, jcodemunch-mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides an independent semantic scan for adversarial approach review, identifying hidden gaps, regressions, or DNA violations that the Planner may have missed.

Core Features & Use Cases

  • Adversarial Review: Performs an independent adversarial review of the refactoring approach.
  • Semantic Understanding: Uses jcodemunch or jCodemunch to verify the approach.
  • Value System: Focuses on semantic integrity, regression detection, DNA hardening, and independent verdict.
  • Use Case: After refactoring, use this Skill to ensure that the approach adheres to all necessary rules and does not introduce any issues.

Quick Start

Run the epic-scan skill with the epic-slug of the approach you want to review.

Frequently Asked Questions about epic-scan

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

FAQPage Schema
How do I conduct an independent semantic scan to find hidden gaps after refactoring?

To conduct an independent semantic scan, use this Skill to perform an adversarial review of your refactoring approach, identifying hidden gaps and regressions the Planner may have missed.

What is adversarial approach review in code analysis?

Adversarial approach review is an independent semantic scan that verifies a refactoring approach to detect hidden gaps, regressions, or DNA violations that the initial Planner may have overlooked.

How do I check my refactored code for wait-free and bounded-latency rule violations?

To check for wait-free and bounded-latency rule violations, run the semantic scan using jcodemunch to verify your refactoring approach adheres to the necessary hardening rules and semantic integrity.

Can I use jcodemunch to verify semantic integrity and detect regressions?

Yes, you can use jcodemunch for semantic verification during the adversarial review process to detect regressions, harden DNA, and provide an independent verdict on your refactoring approach.

When should I run an adversarial review for DNA hardening?

You should run an adversarial review for DNA hardening immediately after refactoring to ensure your approach does not introduce issues and adheres to all necessary wait-free and bounded-latency rules.