메뉴
Create human-readable Klimkit walkthrough proof reports with steps, screenshots, links, redaction checks, and report-server/Tailscale handoff. Use when a user asks for a walkthrough, proof report, demo evidence, QA narrative, or review packet.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | klimkit-walkthrough |
| description | Create human-readable Klimkit walkthrough proof reports with steps, screenshots, links, redaction checks, and report-server/Tailscale handoff. Use when a user asks for a walkthrough, proof report, demo evidence, QA narrative, or review packet. |
Create a small static HTML report that lets a human inspect what happened without reading the whole conversation.
docs/work/ layout, use klimkit-setup first.docs/work/ phase folder (e.g. 003-walkthrough.html). Keep heavy media in the phase folder's gitignored .local/ subfolder unless it is irreproducible evidence.klimkit-report-server for local or Tailscale serving.LOG.md and the final handoff.Read references/walkthrough-report.md for the first-pass HTML structure and proof checklist.
Convert an implementation, debugging, release, UI, backend, security, or research request into a concrete pass/fail acceptance checklist before code changes start. Use when Codex needs blocking success criteria, scope boundaries, verification targets, or a task note for Klimkit-managed work.
Diagnose bugs, failures, flaky behavior, broken tests, CI failures, or unexpected production signals with a reproduce-first workflow and Klimkit proof. Use when the user asks to debug, investigate, root-cause, fix a failure, or explain why behavior changed.
Interview the user relentlessly about a plan, design, architecture, product decision, workflow, or release choice until shared understanding is reached, using repo and web research to prioritize the most important unresolved questions while recording the considered question shortlist, each asked question, and each approved decision in a Klimkit task note. Use when the user asks to be grilled, stress-test a plan, resolve design branches, clarify tradeoffs, or turn vague intent into explicit decisions.
Run Klimkit's full implementation workflow for code, docs, release, configuration, UI, backend, security-sensitive, or proof-producing changes. Use when the user asks Codex to implement, fix, refactor, release, migrate, wire up, or complete non-trivial repository work with checklist, verification, reflection, and final review.
Write a concise cross-task reflection note after verification and before final review for non-trivial Klimkit work. Use when Codex should connect the current task to prior work history, patterns, risks, or future process improvements.
Check, explain, or set up Klimkit static proof-report serving for `docs/work` HTML reports and Tailscale URLs. Use as the fallback when native hosted publishing (Claude Code Artifacts, Codex Sites) is unavailable and a task needs report-server readiness, `/reports/` links, Tailscale Serve verification, or troubleshooting report visibility.