Use for AST search and codemods. Triggers: ast-grep, sg, function/call/class/import, empty catch, missing await, YAML rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use for manual web, TUI, CLI, API and desktop QA. Triggers: smoke test, visual QA, screenshot check, CJK clipping, 수동 QA, 실제로 되는지 확인, 동작 확인, 직접 돌려봐.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Prove a built surface works by DRIVING it, not by inferring from green tests. No scenario closes on a status string; it closes on a captured artifact from a real surface, an adversarial pass, and a teardown receipt. Everything in this skill is E7 discipline (agent-followed, not hook-enforced); the one shipped E2 touchpoint is noted in §7.
Completion proof: dev verification gate (FAMILY-PROOF-01). Every PASS points at a non-empty artifact you (or your dispatched QA worker) captured THIS round.
State the exact surface and invocation BEFORE running each scenario. Use the channel faithful to the surface — CLI output parsed from the wrong layer is not evidence of the layer you changed:
| Surface | Faithful channel | Artifact |
|---|---|---|
| HTTP API | curl -i (headers + body) — scenarios in references/http-api-qa.md | response capture |
| CLI | real invocation, stdout/stderr split + exit code — discipline in references/cli-tui-qa.md | terminal capture |
| TUI | tmux session at FIXED dims — mechanics in references/cli-tui-qa.md, visual rubric in references/visual-qa.md | plain + ANSI captures |
| Web UI | browser screenshot at a STATED viewport, read via view_image — workflow in references/visual-qa.md | screenshot(s) |
| Desktop GUI | computer-use + screenshots (per-app approval; never drive terminals/Codex itself) | screenshots + action log; native panels, menu-bar popups and approval prompts follow dev-devops native-desktop-acceptance.md §10 and macos-system-approvals.md |
Tool choice for the browser/CU rows follows the shared portable browser policy; the inspect -> act -> re-inspect protocol applies. Data-shaped behavior may use parsed CLI/data output as its channel.
Read the matching row before the governed action.
| Condition | Reference |
|---|---|
| Choosing QA ownership or closing PABCD C | Scope and binding |
| Recording any scenario verdict or aggregate receipt | Evidence contract |
| Driving scenarios and reviewing artifacts | Adversarial classes and oracle passes |
| Finishing any QA pass | Teardown receipts |
| ANY visual surface verdict (web UI, TUI, desktop GUI) | Visual rubric |
| HTTP API surface scenarios | Wire-driving procedure |
| CLI or TUI surface scenarios | Session mechanics |
| Choosing browser/CU tools | Portable browser routing (QA-TOOL-LADDER-01) |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use for AST search and codemods. Triggers: ast-grep, sg, function/call/class/import, empty catch, missing await, YAML rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use for coding, PR delivery, scaffolding and QA. Triggers: develop, fix, refactor, test, review, docs, browse, stacked PR, 개발, 수정, 검토, 스택 PR.
日本語の概要は準備中です。原文の説明を表示しています。
Use for module boundaries and dependencies. Triggers: circular import, coupling, barrel, re-export, validation placement, 모듈 경계, 순환 참조.
日本語の概要は準備中です。原文の説明を表示しています。
Use for APIs, servers and app databases. Triggers: REST, GraphQL, migration, query optimization, middleware, caching, queues, 백엔드, API 작업, 마이그레이션, 쿼리 최적화.
日本語の概要は準備中です。原文の説明を表示しています。
Use for code/PR/diff review and refactor audits. Triggers: review this, before merge, antipattern, 리뷰, 코드 리뷰, 머지 전에 확인.
日本語の概要は準備中です。原文の説明を表示しています。
Use for analytics and data pipelines. Triggers: ETL, ELT, data quality, SQL optimization, schema drift, backfill, 데이터 파이프라인, 데이터 품질, 백필.
日本語の概要は準備中です。原文の説明を表示しています。