Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scans staged changes for secrets, debug statements, TODOs without references, and other common commit mistakes. Use before creating any commit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Catch the easy mistakes before they enter history.
vibe-publication-leak-guard)Pattern-matching a diff by eye misses things that a deterministic scanner catches. Before the manual checks:
pre-commit run, lefthook, husky, or a lint/check script. Check .pre-commit-config.yaml, package.json, and the Makefile.gitleaks protect --staged, trufflehog git file://. --since-commit HEAD) or vibe-cli pre-commit from this repo.vibe-cli hook install, or a gitleaks pre-commit hook), then fall back to the manual checks below.Tool findings are blocking. The manual checks cover what the tools don't.
Scan for patterns:
API_KEY=, SECRET=, PASSWORD=, TOKEN=AKIA[0-9A-Z]{16}-----BEGIN.*PRIVATE KEY-----.env files being stagedconsole.log(, fmt.Println(, print(, debugger;// DEBUG, # DEBUG, /* DEBUGlog.Debug in non-debug code pathsTODO without issue number: TODO: fix this (bad)TODO(#123): fix this (good)FIXME, HACK, XXX — flag allt.Skip(, xit(, xdescribe(, @pytest.mark.skip//nolint without justificationStatus: CLEAN / WARNINGS / BLOCKED
Tools run: [e.g., pre-commit run, gitleaks protect --staged, or "none configured"]
| Check | Status | Findings |
|---|---|---|
| Scanner / hooks | ✓/✗/n/a | X findings |
| Secrets | ✓/✗ | X patterns found |
| Debug statements | ✓/✗ | X occurrences |
| TODOs | ✓/◐ | X without references |
| Disabled tests | ✓/✗ | X found |
| Large files | ✓/✗ | X over limit |
| Commented code | ✓/◐ | X blocks |
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Catches shortcuts and reward hacking — weakening or deleting tests to make them pass, hard-coding expected outputs, silently dropping requirements, or claiming work is done without running it. Use before declaring a task complete and whenever a test or requirement feels like it's in the way.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.