Theater Detection Audit FAQs

Question 1

What is 'code theater' in the context of this skill?

Accepted Answer

Code theater refers to elements like mock data, hardcoded responses, and empty stub functions that simulate functionality without containing actual production logic. This skill identifies these 'performative' pieces of code so they can be replaced with real implementations.

Question 2

When should I use the Theater Detection Audit skill?

Accepted Answer

This skill is best used during pre-deployment reviews, when transitioning from a prototype to a production environment, or when inheriting a legacy codebase where you need to distinguish between real logic and temporary placeholders.

Question 3

How does this skill improve my development workflow?

Accepted Answer

It automates the tedious process of hunting for TODOs, FIXME markers, and hardcoded 'test' values. By providing a structured audit report and risk assessment, it helps you prioritize critical technical debt and ensures no mocks accidentally reach production.

Question 4

Does it handle complex code dependencies?

Accepted Answer

Yes. The skill includes a dependency mapping phase that identifies when one placeholder (like a mock API) supports multiple stubs, allowing you to resolve code completions in the most efficient logical order.

Question 5

What kind of patterns can this skill detect?

Accepted Answer

It identifies a wide range of patterns including standard markers (TODO, HACK, XXX), suspicious constants (test emails, dummy IDs), functions that return hardcoded arrays, and oversimplified error handling that masks real failures.

Theater Detection Audit

Theater Detection Audit

主要功能

使用场景

主要功能

使用场景