pandahrms

ALWAYS use when the user needs to create, start, or checkout a new git branch. Prevents dangerous upstream tracking inheritance and enforces folder-based naming conventions. Triggers on any mention of new branch, new feature branch, branching off, or checkout -b

Manually invoked as `/card-commit` (or by an explicit mention of "card-commit" / "commit this card") to commit ONLY the current card's slice of changed files -- not the whole branch. Trusts the card's pre-complete `/verify` already returned `VERIFY RESULT: PASS` on this tree with no edits since: runs format + lint, but does NOT re-run the test suite or build. If any edit landed after that PASS (or the PASS cannot be confirmed), invokes `/verify` first and requires PASS before committing. Plans and executes atomic commits of the card's files with a conventional message and no AI attribution. Never pushes, never opens a PR, never amends or runs destructive git. Does NOT auto-trigger -- only on the `/card-commit` slash command or an explicit "card-commit"/"commit this card" mention; a finished card alone is not enough.

Manually invoked as `/close` to close a finished piece of Pandahrms work after every card is executed. Verifies every card is already in the per-work `done/` folder and STOPS if any card remains in `active/`; for ticket-driven work invokes `/resolve-ticket` to move the ticket to a resolved, ready-for-release state (status + solution, dev status, Developer Resolution, customer comment); writes the docspace dev-diary log and updates progress; marks the work closed in the per-work `_overview`. Mutating -- it changes ticket state and writes the log. Does NOT move cards. Does NOT raise PRs (that is `/pr`). Does NOT auto-trigger -- only on the slash command or an explicit "close this work" mention.

Triggers on mentions of code review of working-tree changes -- "review my changes", "check my changes", "review the diff", "review before commit". If the user is ambiguous between working-tree review and PR review, ask which one they mean. A diff-scoped LLM-JUDGMENT review only -- SOLID intent, naming meaning, semantic reuse, audit-pattern conformance, input-validation adequacy, PII/data-exposure, error-handling adequacy, readability, and spec MEANING. Reads all changed files, reviews against the judgment checklist, fixes issues, dispatches a Codex second opinion when the diff warrants it, and runs /simplify. Does NOT run the linter, build, tests, or deterministic guards -- those belong to /lint-gate and /verify; when a /lint-gate result is provided, code-review consumes its `OWNED:` line and drops the matching judgment rows, merging its `[tool:*]` findings as context. Does NOT commit directly. Supports `--approve` to auto-pick the "proceed" choice at every AskUserQuestion, and `--skip` to forward to `/commit --skip` at Phase 7. `--codex` / `--no-codex` force the Codex second opinion on or off.

Triggers when the user explicitly requests a git commit of the whole branch's working-tree changes -- phrases like "commit my changes", "git commit", "ready to commit", "/commit", or "make atomic commits". Branch-scope commit step: a clean-tree gate over the whole branch that auto-fixes format + lint inline, then invokes `/verify` (the project-scoped build + test runner) and requires `VERIFY RESULT: PASS` before planning and executing atomic commits across the branch. The gate applies even to pre-existing or unrelated failures. Supports `/commit --skip` to bypass the entire Phase 1 gate (format, lint, and the `/verify` build + test run).

2 hooks across 2 events