メニュー
Fake code detection — performative implementations, test theater, misleading patterns, red flags
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/JSai23/claude-tooling --skill verify-larp-aコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.
SKILL.md を表示中
SOC 職業分類に基づく
| name | verify-larp-a |
| type | action |
| description | Fake code detection — performative implementations, test theater, misleading patterns, red flags |
| user-invocable | false |
Action skill — Fake code detection procedures: performative code, test theater, red flags, output format.
How to identify code that lies — performative implementations that look correct but don't actually work.
Performative implementation — Stubs returning hardcoded values. Validation that always returns true. Error handling that swallows (catch (e) {}). Retry logic that doesn't retry. Async without await. Functions under 5 lines that should be complex.
Test theater — Mocking the thing being tested. Assertions that assert nothing (assert(true)). Tests changed to match broken behavior. Skipped tests with eternal TODOs. 100% coverage achieved by testing trivial paths only.
Misleading patterns — Comments that contradict the code. Function names that lie. "Temporary" hacks with no removal plan. Happy path only — works for the demo, crashes on real input.
Automatic suspicion: TODO, FIXME, pass, ..., NotImplementedError. Functions under 5 lines that should be complex. Empty catch blocks. Promise chains that drop errors. Timeouts set to unreasonably large values.
Critical — will fail in production with user-visible impact. Stubs, missing error handling.
Warning — works but is deceptive. Tests that don't verify real behavior, incomplete validation.
Suggestion — technically correct but suspiciously simple. Under-implemented functions, unconsidered edge cases.
### [CRITICAL|WARNING] {title}
FILE: {path}:{line}
THE LIE: What the code pretends to do
THE TRUTH: What actually happens
EVIDENCE: The actual code snippet
IMPACT: What breaks when this lie is discovered in production
Finding no fake code is valid — report "No fake code detected" and stop.