メニュー
Demo skill that hunts two seeded bugs in a tiny stats package until its tests go green, then files a detective-style CASE_FILE.md with the evidence.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/decodingai-magazine/building-a-coding-agent-from-scratch-course --skill demo-2-bug-huntコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Demo skill that web-fetches two Decoding AI knowledge-graph articles, has the agent itself distill them into a typed entity/relation graph, and renders an interactive dark-themed force-directed KG into one self-contained kg.html — no graph library, no CDN.
Manual end-to-end QA playbook for decode against a real provider — what to type at each surface (chat, gated read/write, bash, todo, web_fetch, ask_user, lsp, agent subagents, docker/modal sandboxing, headless `decode run`, HITL, model override, replay, mid-turn steer/abort, persistence/memory, /ship, sandbox git token) and what "working" looks like. Use when manually testing or verifying a decode surface end-to-end.
Demo skill for the meta "decode improves decode" flow — launch decode in a sandboxed clone of the course repo, plan and build one small feature inside the Workspace, let Hand-back push the Session Branch, then open a draft PR against the course repo.
| name | demo-2-bug-hunt |
| description | Demo skill that hunts two seeded bugs in a tiny stats package until its tests go green, then files a detective-style CASE_FILE.md with the evidence. |
Play detective on a small statistics package: reproduce the failures, hunt down the bugs, fix them until every test passes, and file a case report.
rm -rf .decode/outputs/bug-hunt && mkdir -p .decode/outputs && cp -r .decode/skills/demo-2-bug-hunt/references/buggy_repo .decode/outputs/bug-huntcd .decode/outputs/bug-hunt/ && uv run pytest -qExactly two tests fail as committed — one in median, one in variance. Do NOT edit the tests;
they encode the correct behaviour. Fix stats.py instead.
Track the investigation with todo_write (reproduce → suspect A → suspect B → verify → case
file) and tick items off as you close them.
test_stats.py to learn the contract each failing test asserts (the expected values are
the spec).stats.py and locate the defect behind each failure with grep/read. The LSP
diagnostics that surface on your edits will help you catch typos and type slips as you go.median returns the wrong element for odd-length inputs (an indexing off-by-one).variance comes back with the wrong sign (it should never be negative).stats.py — the smallest correct change, not a special case
that only satisfies the one test input.uv run pytest -q and confirm the whole suite is green. Keep that green one-liner too.Write .decode/outputs/bug-hunt/CASE_FILE.md — short, punchy, detective-flavoured:
stats.py:<line>), the root cause in
one sentence, and the before/after of the fixed line.pytest -q summary line proving the suite passes.Report the two root causes, the one-line fix for each, and point the human at CASE_FILE.md.