Render a dashboard of the current Claude Code session — message counts, token usage, cache read/write, dollar cost, context %, lines changed, cost-per-turn sparkline, and a tool-call histogram — parsed from the session transcript JSONL by a bundled bash script. One bash call, zero analysis, zero confirmation. Optionally pass a session id to inspect a different session. Use when the user asks for session stats, usage, token or cost breakdown, or a session dashboard.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
One bash call, then relay. The bundled script finds the transcript at
~/.claude/projects/*/<session-id>.jsonl (current id comes from
CLAUDE_CODE_SESSION_ID in the bash environment), aggregates it with jq,
and prints the dashboard. All numbers come from the script — compute nothing
yourself.
bash {base_directory}/dashboard.sh [session-id]
Print the script's stdout verbatim inside a ```text code fence. After the fence, add at most one sentence — or nothing.
Non-zero exit → print stderr verbatim and stop. No retries, no fallback parsing.
— for fields it can't find. Never "fill in" missing values by reading
the JSONL yourself.! bash {base_directory}/dashboard.sh --color아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Retire a closed issue's working artifacts out of specs/ into the GitHub wiki. Use only when the user asks to archive a finished issue, empty out specs/ for a done task, or move an issue's requirements/architecture/tasks/review/QA docs to the wiki.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
One-shot conventional commit; bundled scripts adaptively gather diff context, draft the message, and stage+commit — pass `ask` to confirm first or add a hint for the title. Use only when the user asks for a commit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Executes a QA specification (specs/qa/QA-<N>-<slug>.md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact QA-RESULTS-<N>-<slug>.md. Use only when the user asks to run or execute a QA plan — never trigger automatically.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
After an issue's PR has squash-merged on GitHub and its issue has closed: fast-forward the default branch, remove the issue-numbered nested worktree (.worktrees/<issue#>), and delete the local feature branch. Use when the user says to finish, tear down, or clean up a lane or worktree for a merged issue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS-<N>-<slug>.md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Phase 4 of 5 — implements tasks from TASKS-<N>-<slug>.md (with ARCH-<N>-<slug>.md as architecture-only context) using mode-appropriate verification (tdd, test-after, ui, checklist); pass 'auto' to run without stepping. Use only when the user asks to run Phase 4 or implement tasks from an ARCH doc — never trigger automatically from a coding request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.