Claude Skills by txreplay

Initialize lightweight tracking for a standalone ticket (not part of an epic). Use when the user invokes "/praxis-bug" followed by a ticket ID (e.g., /praxis-bug KEY-31982). Creates tracking, sets up git, runs triage, and surfaces lessons — all in one step.

Capture an implementation decision or spec correction into the active ticket's tracking file. Use when the user invokes "/praxis-capture" to record decisions that deviate from or complement original specs. Optionally posts to the provider.

Verify whether code changes cover the acceptance criteria of the active ticket. Use when the user invokes "/praxis-check" with or without a ticket ID. Compares implemented code with acceptance criteria and local progression, generates a coverage report.

Close the active ticket with pre-flight verification. Use when the user invokes "/praxis-done" with or without a ticket ID. Runs gates (clean tree, AC coverage, build, TODOs), transitions status on the provider, and moves to the next ticket.

Capture a cross-ticket lesson or surface relevant lessons for the current ticket. Use when the user invokes "/praxis-learn" to record a pattern, or "/praxis-learn --review" to see lessons relevant to the current work.

List all tracked epics and tickets with their status. Use when the user invokes "/praxis-list" to see an overview of all tracked work or switch context between epics.

Initialize local tracking for an epic and all its child tickets. Use when the user invokes "/praxis-new" followed by an epic ID (e.g., /praxis-new KEY-30635). Fetches the epic and its children via the configured provider, creates a folder with one markdown file per ticket + an epic summary file.

Analyze current state and suggest the next action. Use when the user invokes "/praxis-next" or seems unsure what to do next. Reads .current, ticket progression, git state, and recommends the next step.

Break down an epic with no child tickets into user stories, create them on the provider, and initialize local tracking. Use when the user invokes "/praxis-plan" followed by an epic ID that has no sub-tasks yet.

Post a progress comment on the active ticket. Use when the user invokes "/praxis-post" with or without a ticket ID. Generates a comment in French from local advancement, previews it, and posts after explicit confirmation.

Set the active ticket and prepare the git environment. Use when the user invokes "/praxis-start" followed by a ticket ID (e.g., /praxis-start KEY-30636). Updates .current, syncs from the provider, creates a worktree or classic branch (user's choice), and displays ticket status.

Update local tracking files from the provider, git diff, code TODOs, and linked resources. Use when the user invokes "/praxis-sync" with or without a ticket ID. Analyzes code changes to update progression and advancement.

Assess ticket complexity and suggest the right implementation workflow. Use when the user invokes "/praxis-triage" with or without a ticket ID.

Collaborative ideation and design exploration before implementation. Explores user intent, requirements, and design through interactive questioning and example mapping. Use when starting a new feature, designing a component, planning functionality, or when user says "brainstorm", "let''s think about", "design this", "how should we build", "I have an idea". Do NOT use for bug fixes or quick changes (use /praxis-fix), or when a spec already exists (use /praxis-implement).

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/praxis-commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Use when work must land on the shared deployment branch of praxis.json › deploy (a test environment) — "mets sur <env>", "merge sur <env>", "cherry-pick <env>", "push <env>", "tout est sur <env> ?", or after review fixes the QA team must re-test. Do NOT use to push a feature branch or to open a PR (/praxis-ship).

Fix bugs, modify existing features, or implement quick isolated changes with deep exploration. Use for any implementation that does not require a full spec file. Auto-detects bug mode (root cause analysis) vs change mode (implementation plan) from description. Do NOT use when a full spec file exists (use /praxis-implement) or for initial feature design (use /praxis-brainstorm).

Implement features from an existing spec file, phase by phase, with parallel exploration and plan validation. Use when user has a spec file and says "implement phase X", "build from spec", "start development", or references a spec path. Requires a spec file as input. Do NOT use for quick changes without a spec (use /praxis-fix) or for creating the plan itself (use /praxis-spec).

Use when a change must be checked in a real browser against the ticket and the design — "qa local", "qa <env>", "teste en local", "vérifie sur <env>", after a deploy to a shared environment, or as the QA stage of /praxis-ship. Do NOT use for unit tests, nor to write E2E tests.

Génère le rapport d'activité de la semaine (feuille de temps) à partir des commits, PRs, tickets et du suivi praxis, réparti par jour sur la liste d'activités du projet. Utiliser quand l'utilisateur invoque /praxis-report, demande de remplir sa feuille de temps, ou demande « sur quoi j'ai travaillé cette semaine » en vue du reporting. Paramètre optionnel — « semaine dernière » ; défaut = semaine courante.

Review a GitHub PR and produce GitHub-ready review comments with file, line, and markdown. Handles re-reviews after fixes and groups of related PRs. Use when the user asks to review a PR by number, URL, or chat link ("review pr 123", "review-pr #456", "fais une review de la pr 789", "la pr X a été corrigée, refais une review").

Universal code review - auto-detects scope from git changes, spec, commit, or brief. Use after completing tasks, implementing major features, before merging, when stuck (fresh perspective), before refactoring (baseline check), or after fixing complex bugs.

Use when the code of the active ticket is written (or a plan with remaining phases exists) and the user wants it taken to a pull request — "/praxis-ship", "on livre", "commit + PR", "fais la QA et ouvre la PR", or a goal of the form "implémente les phases, /praxis-review, QA, commit, PR". Requires praxis tracking (.current). Do NOT use for the initial plan (/praxis-spec), for triage (/praxis-triage) or for a bug fix without tracking (/praxis-fix).

Create complete development plans and feature specifications with parallel codebase exploration. Use when user says "plan a feature", "create a spec", "write a plan", "design the architecture", or needs a structured spec file before implementation. Do NOT use for quick changes without planning (use /praxis-fix) or for initial ideation (use /praxis-brainstorm first).

Use when implementing any feature or bugfix with strict baby-steps TDD - enforces minimal code and mandatory checkpoints

Use when the user wants the team's PR review-request channel watched — new requests reviewed via /praxis-review-pr, reviewed PRs tracked for fixes and re-reviewed on new commits, the user's own PRs watched for incoming reviews and for a red main after merge. One pass per invocation, designed for /loop. Triggers — "surveille le channel", "watch prs", "/loop /praxis-watch-prs". Do NOT use for a one-off review (/praxis-review-pr) nor for assigned tickets (/praxis-watch-tickets).

Use when the user wants their assigned tickets watched in the background and pre-read before they start them — "surveille mes tickets", "watch my tickets", "/loop /praxis-watch-tickets", "prépare les questions sur mes prochains tickets". One pass per invocation, designed for /loop. Do NOT use to start a ticket (/praxis-start) or to triage one on demand (/praxis-triage).

Use when the user wants one background session watching both the PR review-request channel and their assigned tickets — "lance la veille", "/loop /praxis-watch", "surveille les PR et mes tickets". One pass per invocation, designed for /loop. Do NOT use for a single watcher on demand (/praxis-watch-prs, /praxis-watch-tickets).