praxis

Hand off an existing independent issue that surfaced mid-task to its own Claude Code session in a new cmux workspace, with auto-collected context; that session runs issue→worktree→PR alone. Not for splitting the current task. Triggers on "cmux delegate", "delegate issue", "delegate to new session", "별도 세션", "세션에 위임", "별건으로 빼서".

Bulk recover Claude Code sessions after a crash, power loss, OOM kill, or reboot by scanning the .jsonl files Claude Code persists automatically. Interactive interview chooses recovery scope and layout. Use this when sessions died and you need them back, NOT for restoring an intentionally saved layout. Priority: crash context wins. If the request mentions a crash/power loss/OOM, prefer this skill even when the user also mentions a snapshot — the snapshot may be stale, and .jsonl scan reflects the real final state. Only defer to cmux-resume-sessions when there is NO crash context and the user explicitly wants to rehydrate a saved snapshot. Triggers on "터졌다", "크래시 복구", "크래시 복원", "전원 꺼짐 복구", "OOM 복구", "세션 살려야", "recover cmux", "crash recovery", "power loss recovery", "cmux session recovery".

Restore cmux workspaces from a JSON snapshot saved by cmux-save-sessions. Use this when you want to rehydrate an intentionally saved layout with NO crash context. Crash routing override: if the request mentions a crash, power loss, OOM, or "살려야", route to cmux-recover-sessions instead — even when the user also mentions a snapshot, because the snapshot may be stale and .jsonl scanning reflects the real latest state. Triggers on "resume sessions", "session resume", "session restore", "cmux resume", "restore from snapshot", "rehydrate sessions", "세션 복원", "스냅샷 복구", "스냅샷 복원".

Save cmux session list as a JSON snapshot. Current session excluded by default. Supports save and list commands. Triggers on "save sessions", "session save", "session snapshot", "cmux save", "list snapshots", "snapshot list".

Automate daily cmux session management. Manual commands for status (dashboard) and cleanup (tidy + reorganize), plus init (hook) and report (schedule) automation. Triggers on "cmux session", "session management", "session cleanup", "cmux status", "cmux cleanup", "cmux tidy".

Worktree-aware wrapper for /codex:review. Forces explicit worktree selection when several worktrees are active, preventing silent cwd mismatch, then gates every returned finding: premise verification before fact-modifying edits, flip detection halting A→B→A oscillation, sibling cross-checks for a port or parallel hotfix, a diminishing-returns advisory (PRAXIS_DIMINISHING_RETURNS_N), and a per-finding approval ask. It also reaps leaked openai-codex brokers (PRAXIS_CODEX_REAP=1). Triggers on "codex review", "review codex", "safe review", "/codex-review-wrap", "premise verification", "flip detection", "sibling defect", "sibling cross-check", "diminishing returns", "broker reap", "finding approval", "적용 승인".

Deferred-decision ledger — harvests commit trailers (`Not-tested:`, `Confidence: low`, `Rejected:`, `Directive:`, `Scope-risk:`) and tree compounding comments (`# [PR #N]`) into a single report-only ledger so a "나중에" marker doesn't silently become "영원히 안 함". Triggers on "praxis:debt", "debt ledger", "지연 결정", "deferred decision", "기술 부채 원장", "commit trailer audit".

On-demand home for the pre-merge approval procedure — the three-surface pre-ask probe, grading every open finding by its blocking decoration, carrying the anchor's `Unverified` gaps into a follow-up, and the six-part briefing that ends in an explicit approve-ask. Triggers on "merge briefing", "pre-merge briefing", "머지 브리핑", "머지해도 되나", "approve merge", "pre-ask probe", "merge approval". Do NOT activate on post-merge cleanup (use `worktree-merge-cleanup`) or on "merge conflict resolution".

Bulk recover Claude Code sessions after power loss or tmux crash. Interactive interview to determine recovery scope, layout, and execution mode. Triggers on "recover", "session recovery", "restore sessions", "power recovery".

Reset the current session's strike counter to 0 and clear the recorded violation list. Required after a 3rd strike block before Claude can respond again. Use when the user types "/reset-strikes", "strike 초기화", "clear strikes".

Session retrospect — analyze current Claude Code session against global `~/.claude/CLAUDE.md` rules, identify friction patterns and root causes, propose context-appropriate improvement actions, then execute after user approval. Triggers on "retrospect", "what went wrong", "session review", "session improvement", "what was the issue", "improve".

Report which requirements in the `~/.praxis/docs/specs/` store the current tree does not yet satisfy — runs each requirement's `Verify:` command and classifies it `implemented` / `missing` / `UNKNOWN`. Report-only: no writes, no commits, no issues. Triggers on "spec drift", "spec-drift", "스펙 드리프트", "미구현 요구", "unmet requirement", "what does this spec still need", "requirement status". Do NOT activate on SKILL.md frontmatter drift (that is `codex-review-wrap`'s live-runtime gate) or on deferred-decision trailers (that is `debt`).

Declare a rule violation in the current Claude Code session. Use ONLY when the user says "/strike", "/praxis:strike", "strike 1/2/3", "삼진", or explicitly asks to record a rule violation. Do NOT activate on colloquial uses like "strike a balance" or "strike that". Escalates — strike 1 warning, strike 2 forced review, strike 3 response block.

Show the current session's strike count (0-3) and the list of recorded violation reasons. Use when the user types "/strikes", "strike status", "몇 진", "check strikes".

Pre-implementation input-surface enumeration — before writing a parser/validator/sanitizer/classifier, enumerate every input variant so each becomes a required test case. Triggers on "surface enumerate", "input surface enumeration", "input parser", "input validation", "intent classifier", "정규식 경계", "입력 표면 열거", "multi-PR shared state", "convention guide reflection", "apply lesson". Do NOT activate on "surface a question", "user-facing surface", or merely explaining an existing parser.

Onboarding entry point for new praxis users — introduces the 4 skill categories, maps common scenarios to the right skill, and explains the hook system. Triggers on "praxis 처음", "praxis 사용법", "어떤 skill 부터", "praxis intro", "praxis getting started".

On-demand home for the pre-merge worktree precondition and the unified post-merge cleanup sequence — how to run `gh pr merge --squash --delete-branch` from the base-branch worktree, the submodule `--force` caveat, the squash-ancestry stale-HEAD guard, and the no-`&&`-chain rule. Triggers on "merge cleanup", "post-merge cleanup", "worktree cleanup", "delete-branch merge", "squash-ancestry", "pre-merge worktree", "머지 후 정리", "worktree 정리". Do NOT activate on "merge conflict resolution" or a plain feature-branch "git merge".

Guide for authoring a new praxis SKILL.md — template usage, SRP, trigger keyword design, frontmatter conventions, and Claude/Codex host differences. Triggers on "new praxis skill", "write praxis skill", "add praxis skill", "skill template", "praxis skill spec", "스킬 작성", "새 스킬". Do NOT activate on "add skill section", "skill up", "skill set".