← ClaudeAtlas

using-praxislisted

Onboarding entry point for new praxis users — introduces the 4 skill categories, maps common scenarios to the right skill, and explains the hook system.
devseunggwan/praxis · ★ 1 · AI & Automation · score 70
Install: claude install-skill devseunggwan/praxis
# Using Praxis Welcome to praxis — a set of Claude Code skills for disciplined, fast, resilient development workflow. ## Skill Categories ### Development Tools for code quality and review workflow. | Skill | When to call | | ------------------------ | ---------------------------------------------------------------------------------------- | | `retrospect` | End of session — find friction root causes and create lasting fixes | | `codex-review-wrap` | Before running `/codex:review` in a multi-worktree repo | | `surface-enumeration` | Before writing a parser/validator/sanitizer — every input variant becomes a test case | | `spec-drift` | Wondering what a spec still needs — runs each requirement's `Verify:` command, reports | | `debt` | Audit deferred markers (commit trailers, `# [PR #N]`) before "later" becomes "never" | | `bypass-report` | Reading the bypass-telemetry / hook fire-rate ledgers — which hooks fire, which never do | | `merge-briefing` | Before asking to merge a PR — probe all three finding surfaces, grade, brief, then ask | | `worktree-merge-cleanup` | Merging from a worktree and cleaning up after — right call site, safe teardown | | `tradeoff` | Tradeoff between implementation options, or whether a review finding