ask-userUse when a lead or worker agent needs to send a status update or ask a question to the user, and the destination depends on how the session was launched (Slack topic vs local terminal). Centralizes the routing decision so agent prompts stay clean of "if Slack else AskUserQuestion" branches.
commitStage and commit changes with conventional commit format. Runs formatting, quick test validation, and creates atomic conventional commits. Examples: `/commit`, `/commit --type feat --scope notification --message "add port"`, `/commit --type fix --scope calendar`.
ipc-answerUse to send an answer back to a child lead session that asked a question via parent IPC. The router-Claude sees inbound questions injected as `[ipc id=<uuid> from=<session>] <text>` lines; replying through this skill delivers the answer to the waiting child over the Unix socket the router boots with
pr-reviewReview the current branch's changes against project standards. Loads the project's review checklist + stack-specific rules, reads the diff, and produces a fixed-format report with issues classified by severity and references to file:line.
prPush branch and create or update a Pull Request with architecture diagrams. Runs /review automatically before pushing (mandatory quality gate). Resolves merge conflicts, generates component diagrams, and monitors CI. Examples: `/pr`, `/pr --base main`, `/pr --skip-ci`.
reviewCode quality validation: formatting, tests, coverage, and coding standards. Run standalone to validate current work, or invoked automatically by `/pr` before push. Supports: `fmt` (format & lint), `test` (run tests), `coverage` (validate thresholds), `rules` (check coding standards), or no sub-comma
routerSpawn the main `router` agent in a detached tmux session. Topic is optional — omit it to start without a subscription and subscribe later with subscribe_slack. Hides the `--dangerously-load-development-channels` flag in the wrapper script so the operator doesn't type it on every boot. Use this once
security-auditScan the codebase (or a worktree diff) for hardcoded secrets, exposed config, common injection patterns, and missing input validation. Produces a fixed-format report with severity-classified findings and file:line references. Invoked by `team-lead` when no repo-local security agent exists, or standa
send-session-messageForward a message to a running lead session (tmux or iTerm2) and submit it. Auto-detects the host: tmux first (`tmux has-session`), then iTerm2 (osascript lookup by session name). Pastes the text literally, then fires a SEPARATE submit keystroke so Claude Code's TUI actually processes the message. C
sessionSpawn a Claude orchestrator sub-session in tmux (default) or iTerm2 (via osascript, when IA_TW_TERMINAL=iterm or as fallback if tmux is missing). Defaults to the `lead` agent (`team-workflow:lead`) with worktree provisioning. `--provision clone` switches `lead` to clone-mode (it shallow-clones `--re
sync-docsAudit and auto-update CLAUDE.md files to match the current state of the codebase. Detects drift between documentation and actual code: new services, removed files, changed patterns, outdated commands, stale references. Applies fixes automatically and shows the diff. Use when you want to ensure CLAUD
team-reviewRequest team review for an existing PR. Loads channel + reviewer config from settings.local.json env (or CLAUDE.md fallback), runs a quick standards preflight on the PR, blocks until CI is green, posts a review-request message in Slack mentioning the configured users/groups, and subscribes to the re
worktreeGit worktree management for parallel development. Create isolated worktrees for features, reviews, and hotfixes without switching branches. Supports: `init` (create), `list` (show active), `switch` (change context), `cleanup` (remove merged/stale), `status` (overview). `init` accepts `--repo <path>`