tearitapart
Critical pre-implementation review. Find what AI breaks. Verdict: PROCEED, REVISE, or RETHINK. Triggers: review plan, tear apart, critique, analyze.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- tearitapart
- kernel
- { "kind": "validator", "version": 1, "confirmation": "none", "side_effects": "none" }
- description
- Critical pre-implementation review. Find what AI breaks. Verdict: PROCEED, REVISE, or RETHINK. Triggers: review plan, tear apart, critique, analyze.
- allowed-tools
- Read, Bash, Grep, Glob
- user-invocable
- true
02 资源文件 2
- 参考文档reference/security-research.md15.6 KB
- 参考文档reference/security.md8.5 KB
03 SKILL.md 正文
<skill id="tearitapart">
<purpose> Pre-implementation review. Check Big 5, security, testing, architecture. Goal: find real problems, not generic concerns. </purpose>
<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>
<phase id="1_gather">
- Read plan/spec
- List files to be touched
- Check git status
- Check AgentDB for prior contracts
- Read _meta/research/ for anti-patterns
output: scope: N files tier: 1|2|3 prior_work: contracts, research found </phase>
<phase id="2_big5"> Run Big 5 checks from skills/quality/SKILL.md:
- 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. </phase>
<phase id="3_security"> Load: skills/tearitapart/reference/security.md
critical:
- [ ] No hardcoded secrets
- [ ] Auth tokens in httpOnly cookies
- [ ] Rate limiting
- [ ] HTTPS enforced
injection:
- [ ] SQL: parameterized only
- [ ] XSS: DOMPurify
- [ ] CSRF: tokens on state changes </phase>
<phase id="4_testing"> Load: skills/build/reference/testing.md
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 </phase>
<phase id="5_architecture"> Load: skills/architecture/SKILL.md
verify:
- Follows existing patterns?
- Interface stability?
- Modular boundaries?
- Dependency direction correct? </phase>
<verdict> <PROCEED> No Big 5 violations. Security passes. Tests defined. Output: "PROCEED with caveats: [list]" </PROCEED>
<REVISE> 1-2 Big 5 violations (fixable). Missing security items. Output: "REVISE: [changes with file:line]" </REVISE>
<RETHINK> 3+ Big 5 violations. Fundamental security gaps. No tests. Output: "RETHINK: [why flawed] → [alternative]" </RETHINK>
<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> </verdict>
<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>
</skill>
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.