Self-Critic Skill

The Second Opinion You Always Wanted

The best engineers review their own work before submitting. The problem: it is hard to critique what you just wrote. Familiarity breeds blind spots.

This skill runs a structured self-review workflow �� rigorous, systematic, and merciless. It catches what you missed.

Three commands:

| Command | Checks | Output | |---------|--------|--------| | /self-critic code | Security, correctness, style, maintainability | Severity-ranked issue list | | /self-critic plan | Logic gaps, missing dependencies, unstated assumptions | Gap analysis + critical path | | /self-critic output | Accuracy, completeness, fabrication, tone | Quality verdict | | /�������u | Bilingual EN + Traditional Chinese review | Dual-language critique |

Example: Code Review

?? Critical: Hardcoded JWT_SECRET line 14 �� rotate, move to env var
?? High: No input validation on email field line 47
?? Low: Function validate_user is 67 lines �� consider splitting
? SQL queries use parameterized inputs �� no injection risk
Verdict: Fix then ship

Bilingual Mode for Asian Markets:

Run /�������u for content going to Chinese-speaking audiences:

• Traditional Chinese (���w����) review for HK/TW content
• Checks tone formality, face-preservation, appropriate CTAs
• Catches mixed character sets, awkward direct translations
• Useful for: marketing copy, cold outreach, proposals

Every issue includes: what the problem is, where it is, why it matters. No vague flags.