cc-praxis

Use when the user says "review the code", "check these changes", "review this", "look at staged changes", or invokes /code-review. Also invoked automatically by git-commit skills if no review has been done this session. Applies to Java/Quarkus, TypeScript, and Python projects.

Use when the user says "bump a version", "upgrade dependencies", "check for newer versions", "add a dependency", or "run audit" — for Java/Maven, TypeScript/npm, or Python/pip projects. Routes to the correct package manager based on project type declared in CLAUDE.md.

Use when user wants to create a commit NOW — says "commit this", "commit these changes", "create a commit". Routes to Java or custom project workflows when CLAUDE.md declares those types; falls back to generic commit for all others. Does NOT apply to discussions about past commits or questions about whether to commit.

Use when the commit history contains noise — fixup commits, revert chains, docs wording chores, tiny cleanups — that obscures meaningful history. Also triggered when the pre-push hook flags squash candidates, or invoked on demand via /git-squash on any commit range.

Use when ending a mid-work session (branch stays open) and wanting to preserve context for resumption, OR when a session is beginning and needing to resume from where things left off — says "create a handover", "end of session", "update the handover", "write a handover", "wrap", or "resume handover". NOT for branch closure (use work-end — it includes the full wrap). NOT for project narrative (use write-content, diary type).

Use when setting up GitHub issue tracking, planning implementation work (creating epics and child issues from a plan), when a user request spans multiple concerns that should be separate issues, or when staged changes span multiple issues and should be split. Also invoked automatically throughout the development lifecycle when Work Tracking is enabled in CLAUDE.md.

Use when correctness, completeness, or consistency of a project needs verification — "is the project healthy?", "pre-release check", "do a health check", "check docs are in sync", invokes /project-health. NOT for improvement suggestions (use project-refine for that).

Use when project setup needs to be verified or completed — invoked automatically at session start (via hook) and by work-start before any branch work begins. NOT invoked directly by users.

Use when seeking improvement opportunities in a project — "find duplication", "bloat check", "look for ways to improve docs", "do a refine session". NOT for correctness or compliance — use project-health for that.

Use when publishing blog entries to external platforms via blog-routing.yaml — user says "publish blog", "publish entries", "cross-post this entry", or invokes /publish-blog. NOT for writing new entries (use write-content with diary type for that).

Use when mapping an existing git repository's history to GitHub epics and issues — user says "map our history to issues", "retrospectively create issues", "backfill GitHub from git log", or invokes /retro-issues. One-off, on-demand only. Never auto-triggered.

Use when user explicitly requests "security review", "audit security", "check for vulnerabilities", or "OWASP check", or when code-review identifies auth/payment/PII code needing a security pass. NOT automatic — must be explicitly requested or offered by code-review. Applies to Java/Quarkus, TypeScript, and Python projects.

Use when CLAUDE.md needs updating due to workflow or convention changes, or when invoked automatically by git-commit/java-git-commit when commits affect build commands, testing patterns, naming conventions, or repository structure.

Use when the user says "update the design doc", "sync DESIGN.md", "sync ARC42STORIES.MD", "reflect code changes in the design", or invokes /update-design. Also invoked by git-commit when commits affect architecture. Routes to the appropriate design doc workflow based on project type.

Use when the current branch is complete and ready to close — user says "work-end", "close this branch", or "wrap up this issue". Must be invoked from the working branch, not main. Replaces "epic close".

Use when interrupting current branch work to switch to something else — user says "work-pause", "pause this work", or "switch to a different issue". Supports a stack of paused branches. Pair with work-resume to restore.

Use when returning to a paused branch — user says "work-resume", "resume", or "go back to that branch". Invoked from main to restore a previously paused work session. Handles multiple paused branches via stack.

Use when the user says "work", "work end", "work pause", or "work resume" — detects current branch state and routes to the correct work lifecycle skill automatically. "work" alone starts new work or shows the pause stack. "work end" closes the branch. "work pause" saves state. "work resume" shows the stack and returns to a paused branch. Replaces needing to know which lifecycle skill to invoke.

Use when a task or session is beginning — the opening directive in any work-item prompt, or when the user says they are beginning work. Handles both new and existing branches. NOT optional, must NOT be skipped.

Use when explicitly creating a new companion workspace from scratch — user invokes /workspace-init or says "init workspace for [project]" or "create workspace for [project]". NOT for questions about workspaces, NOT for ongoing use, NOT for modifying existing workspaces. One-time setup only.

Use when writing any piece of content — project diary entry, blog post, article, note, brief, README, news item, technical documentation section, or essay. User says "write", "draft", "write a diary entry", "log what we built", "document this pivot", "blog all the work to date", "create a post", "write up", "write the README", "rewrite the README", or provides a topic/subject to write about. Documentation types (tutorial, how-to, explanation, reference) are in scope. NOT for generating code (use java-dev, ts-dev etc.).

Use when documentation needs syncing — user says "sync docs", "update docs", "doc sweep", or invoked from a prompt snippet at session end. Scoped to what changed this session only, not a full project sweep. NOT a design journal update (java-git-commit handles that).

Use when CI is red and the user asks to fix it, or when a push fails CI and the user asks "is CI green?" after a fix. Ensures all failures are reproduced locally, root-caused, and verified green before any push. Never use CI as a test runner.

Use when recording architectural decisions: user says "create an ADR", "document why we chose X", significant technical choices are made, dependency-update proposes major version upgrades, or update-design captures new components.

Use when writing new Java code, fixing bugs, refactoring, or adding tests in Quarkus applications — user says "implement", "fix", "refactor", or "add tests", or is editing .java files, pom.xml, or build.gradle. Does NOT apply to reading/discussing code without changes. For code review use code-review; for commits use git-commit.

Use when writing new Python code, fixing bugs, refactoring, or adding tests — user says "implement", "fix", "refactor", "add tests", or is editing .py files, pyproject.toml, requirements.txt, or setup.py. Does NOT apply to reading or discussing existing code without changes.

Use when writing new TypeScript code, fixing bugs, refactoring, or adding tests — user says "implement", "fix", "refactor", "add tests", or is editing .ts, .tsx, tsconfig.json, or package.json files. Does NOT apply to reading or discussing existing code without changes.

INVOKE IMMEDIATELY when two IntelliJ MCPs are visible: mcp__intellij-index__* and mcp__intellij__*. These are NOT interchangeable — mcp__intellij-index__ supports auto-opening projects via project_path; mcp__intellij__ cannot. Always use mcp__intellij-index__ for code navigation. Never try mcp__intellij__ first and fall back. Also invoke for any IDE operation: rename, move file, find references, navigate to definition, type hierarchy, diagnostics.

Use when user wants to park an idea for later — says "log this idea", "add to idea log", "park that thought", "we should consider this someday", or "capture that for later". NOT for decisions already made (use adr), or active implementation planning.

Use when the user wants to sync installed skills to the latest version from the cloned repository — says "sync skills", "update installed skills", "sync local", or invokes /sync-local. DEV-ONLY: requires a cloned repository with scripts/claude-skill on PATH. Not available to marketplace plugin installs.