인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
개발 및 엔지니어링 · SKILL.md

tearitapart

tearitapart

Critical pre-implementation review. Find what AI breaks. Verdict: PROCEED, REVISE, or RETHINK. Triggers: review plan, tear apart, critique, analyze.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: tearitapart description: "Critical pre-implementation review. Find what AI breaks. Verdict: PROCEED, REVISE, or RETHINK. Triggers: review plan, tear apart, critique, analyze." user-invocable: true allowed-tools: Read, Bash, Grep, Glob kernel: kind: validator version: 1 side_effects: none confirmation: none

<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

  1. input_validation: Zod schema? Parameterized queries?
  2. edge_cases: null, empty, unicode, timeout?
  3. error_handling: no empty catch? Logged with context?
  4. duplication: same logic repeated?
  5. 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>

저장한 Skills