Skill Debug Review FAQs

Question 1

What exactly does the debug-review skill check?

Accepted Answer

It validates skill structure, cross-references between orchestrators and perspectives, project-specific content density, instruction clarity, and compliance with mandatory review templates.

Question 2

What happens if a skill fails the validation check?

Accepted Answer

The debug-review skill generates a detailed report identifying missing mandatory elements or structural issues, allowing you to refine your generation parameters or fix the skill manually.

Question 3

When is the best time to use this skill?

Accepted Answer

It is designed to run automatically after the build-skills process, but you can trigger it manually whenever you update your project's knowledge base or review patterns.

Question 4

How does it ensure reviews aren't generic?

Accepted Answer

The skill includes a Specificity Validation check that flags skills if they lack project-specific references like file paths, module names, or unique architectural patterns found in your knowledge base.

Question 5

Does it check for all technical concerns?

Accepted Answer

Yes, it verifies the presence of the 8 mandatory technical concerns: execution-flow, resource-management, concurrency, security, platform-constraints, implementation-quality, code-health, and strategic-alignment.

Skill Debug Review

主要功能

使用场景

Skill Debug Review

主要功能

使用场景