hashgraph-online/awesome-codex-plugins / plugins/ariaxhan/kernel-claude/skills/tearitapart
tearitapart
UnverifiedCritical pre-implementation review. Find what AI breaks. Verdict: PROCEED, REVISE, or RETHINK. Triggers: review plan, tear apart, critique, analyze.
<skill_load> Load: skills/quality/SKILL.md, skills/build/reference/testing.md, skills/tearitapart/reference/security.md Reference: skills/quality/reference/quality-research.md </skill_load>
<on_start>
agentdb read-start
</on_start>
output: scope: N files tier: 1|2|3 prior_work: contracts, research found
- input_validation: Zod schema? Parameterized queries?
- edge_cases: null, empty, unicode, timeout?
- error_handling: no empty catch? Logged with context?
- duplication: same logic repeated?
- complexity: functions < 30 lines?
Use quick_checks from quality skill for detection.
critical:
- No hardcoded secrets
- Auth tokens in httpOnly cookies
- Rate limiting
- HTTPS enforced
injection:
- SQL: parameterized only
- XSS: DOMPurify
- CSRF: tokens on state changes
verify:
- Tests exist BEFORE implementation?
- Edge cases covered?
- Assertions specific (not toBeTruthy)?
- Mocks at boundaries only?
red_flags:
- "Will add tests later"
- 100% coverage, weak assertions
- No error path testing
verify:
- Follows existing patterns?
- Interface stability?
- Modular boundaries?
- Dependency direction correct?
<ask_user> Use AskUserQuestion when: verdict is REVISE or RETHINK Ask: "Verdict: {REVISE|RETHINK}. Want details on specific findings, or proceed with fixes?" Options: show details, proceed with fixes, override and proceed anyway </ask_user>
<output_format>
Save to _meta/reviews/{feature}-teardown.md:
# Tear Down: {feature}
reviewed: {timestamp}
tier: {1|2|3}
scope: {N files}
## Big 5
input_validation: pass|fail
edge_cases: pass|fail
error_handling: pass|fail
duplication: pass|fail
complexity: pass|fail
## Verdict: PROCEED | REVISE | RETHINK
{reasoning}
## Action Items
1. {fix with file:line}
</output_format>
<on_complete>
agentdb write-end '{"command":"tearitapart","verdict":"X","big5_violations":N}'
</on_complete>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |