Slash Commands Reference

Overview

Pi provides two types of slash commands:

• Prompt template commands — defined in the prompts/ directory, executed by the orchestrator, and may delegate to specialist agents.
• Extension commands — defined in TypeScript under extensions/orchestrator/, executed directly without an AI roundtrip (unless noted).

All commands support Tab completion for arguments. Completions are cached for 5 minutes.

Implementation Commands

/implement

Runs a scout, planner, and worker agent chain to explore the codebase, plan changes, and implement them.

/implement <task>

The command executes three agents in sequence:

1. scout — explores the codebase and returns a summary of file locations, key functions, and dependencies.
2. planner — creates a detailed implementation plan: files to modify, step-by-step changes, edge cases, testing approach.
3. worker — implements the plan, making all code changes following project conventions.

/implement add pagination to the /users API endpoint

/scout-and-plan

Runs the scout and planner agents without implementing. Useful for reviewing a plan before committing to changes.

/scout-and-plan <task>

The command executes two agents in sequence:

1. scout — explores the codebase and returns a summary of relevant code.
2. planner — creates a detailed implementation plan with files, steps, edge cases, and testing approach.

/scout-and-plan migrate the auth middleware to use JWT tokens

/implement-and-review

Implements a task, runs three parallel code reviewers, then fixes all issues found.

/implement-and-review <task>

The command executes agents in this sequence:

1. worker — implements the task.
2. Three review agents run in parallel:
3. code-reviewer-quality — code quality review
4. code-reviewer-guidelines — guideline adherence review

5. code-reviewer-security — bugs and security review

6. worker — fixes all issues found by reviewers and reports what was fixed.

/implement-and-review add rate limiting to the API gateway

Code Review Commands

/pr-review

Reviews a GitHub PR using three parallel review agents and posts inline comments.

/pr-review [PR number or URL]

Tab completion: Open PR numbers from the current repository.

Prerequisites: uv and myk-pi-tools must be installed.

Workflow phases:

1. PR Detection — resolves the PR from the argument or current branch via gh pr view.
2. Data Fetching — fetches the PR diff and project AGENTS.md using myk-pi-tools pr diff and myk-pi-tools pr claude-md.
3. Code Analysis — delegates to three review agents in parallel (quality, guidelines, security).
4. User Selection — presents findings grouped by severity (CRITICAL, WARNING, SUGGESTION). The user selects which to post.
5. Post Comments — posts selected findings as inline PR comments via myk-pi-tools pr post-comment.
6. Summary — displays final counts and links.

/pr-review
/pr-review 123
/pr-review https://github.com/owner/repo/pull/123

/review-local

Reviews uncommitted changes or branch differences using three parallel review agents.

/review-local [base branch]

Tab completion: Git branch names (local and remote).

When no argument is provided, reviews all uncommitted changes (staged + unstaged) via git diff HEAD. When a branch is specified, compares the current branch against it via git diff <branch>...HEAD.

Three review agents run in parallel, analyzing for code quality, guidelines adherence, and security. Results are merged, deduplicated, and presented grouped by severity.

/review-local
/review-local main
/review-local feature/auth-refactor

/review-handler

Processes all review sources (human, Qodo, CodeRabbit) from the current branch's PR and applies fixes.

/review-handler [--autorabbit] [URL]

Tab completion: --autorabbit flag.

Prerequisites: uv and myk-pi-tools must be installed.

Warning: --autorabbit is a command-level flag. It is never passed to myk-pi-tools CLI commands.

Standard workflow:

1. Fetches reviews from all sources via myk-pi-tools reviews fetch.
2. Presents items in a table grouped by source, with global numbering and priority sorting.
3. Collects user decisions (yes/no/all/skip per source).
4. Delegates fixes to appropriate specialist agents.
5. Runs tests (all must pass before proceeding).
6. Commits and pushes changes.
7. Posts replies to GitHub and stores results in the database.

Autorabbit mode (--autorabbit):

Skips the initial fetch/review cycle and enters a polling loop. CodeRabbit comments are auto-approved without user interaction. The loop runs until CodeRabbit approves the PR or the user explicitly stops it.

/review-handler
/review-handler --autorabbit
/review-handler https://github.com/owner/repo/pull/123#pullrequestreview-456

/refine-review

Refines pending GitHub PR review comments with AI before submitting.

/refine-review <PR URL>

Prerequisites: uv and myk-pi-tools must be installed.

Workflow:

1. Fetches pending review comments via myk-pi-tools reviews pending-fetch.
2. Refines each comment for clarity, conciseness, and actionability.
3. Presents original and refined versions side-by-side.
4. User selects which refinements to accept (all, specific numbers, keep originals, or custom text).
5. User chooses a review action: Comment, Approve, Request Changes, or keep pending.
6. Submits updates via myk-pi-tools reviews pending-update.

/refine-review https://github.com/owner/repo/pull/123

Release & Integration Commands

/release

Creates a GitHub release with automatic changelog generation and optional version file bumping.

/release [version] [flags]

Tab completion: Recent git tags sorted by version.

Prerequisites: myk-pi-tools must be installed.

Workflow:

1. Validation — checks branch status, clean working tree, and remote sync via myk-pi-tools release info.
2. Version Detection — scans for version files via myk-pi-tools release detect-versions.
3. Changelog — categorizes commits by conventional commit type and generates formatted changelog with emoji section headers.
4. User Approval — presents proposed version, version files to update, and changelog preview. Skipped when an explicit version is provided.
5. Version Bump — updates version files via myk-pi-tools release bump-version, creates a PR, and merges it.
6. Create Release — creates the GitHub release via myk-pi-tools release create.

Version bump logic:

/release
/release 2.0.0
/release --dry-run
/release --prerelease --draft

/coderabbit-rate-limit

Handles CodeRabbit rate limits by waiting for the cooldown period and re-triggering the review.

/coderabbit-rate-limit [PR number or URL]

Tab completion: Open PR numbers from the current repository.

Prerequisites: uv and myk-pi-tools must be installed.

Workflow:

1. Detects the PR from arguments or current branch.
2. Checks rate limit status via myk-pi-tools coderabbit check.
3. If rate-limited, waits for the cooldown (plus 30-second buffer) and triggers @coderabbitai review.
4. Polls until the review starts (max 10 minutes).

/coderabbit-rate-limit
/coderabbit-rate-limit 123
/coderabbit-rate-limit https://github.com/owner/repo/pull/123

/query-db

Queries the reviews database for analytics and insights about PR review history.

/query-db <command>

Prerequisites: myk-pi-tools must be installed.

Available subcommands:

Note: Only SELECT statements and CTEs are allowed. Modifying queries (INSERT, UPDATE, DELETE, DROP) are blocked.

The database is located at <project-root>/.claude/data/reviews.db.

/query-db stats --by-source
/query-db stats --by-reviewer
/query-db patterns --min 2
/query-db dismissed --owner myorg --repo myrepo
/query-db query "SELECT * FROM comments WHERE status='skipped' LIMIT 10"

External Agent Commands

/acpx-prompt

Runs a prompt through acpx to any ACP-compatible coding agent.

/acpx-prompt [agent[:model]] [--fix|--peer] <prompt>

Tab completion: Agent names (pi, openclaw, codex, claude, gemini, cursor, copilot, droid, iflow, kilocode, kimi, kiro, opencode, qwen) and flags (--fix, --peer).

Prerequisites: acpx must be installed (npm install -g acpx@latest). The underlying agent CLI must also be installed separately.

Supported agents:

Modes:

Note: --fix and --peer are mutually exclusive. Multiple agents with --fix is not supported.

Peer review mode runs a multi-round debate loop between Claude and the peer agent(s). Claude fixes code based on findings and sends changes back for re-review. The loop continues until all peer agents confirm no remaining issues. With multiple peers, all must agree independently.

Configuration persistence: The last-used agent spec is saved to .pi/acpx-config.json after successful runs. Subsequent invocations without an agent name use the saved value.

/acpx-prompt codex review this function
/acpx-prompt cursor:gpt-4o --fix fix the failing tests
/acpx-prompt cursor,codex --peer review the architecture
/acpx-prompt --peer review this code

Memory Commands

/dream

Runs memory consolidation as a background async agent. Analyzes the current session and maintains the memory.md file.

/dream

This command takes no arguments. It runs as a fire-and-forget background agent and does not block the session.

Operations performed:

1. Reads the memory file at <project>/.pi/memory/memory.md.
2. Extracts learnable items from the current session (lessons, preferences, mistakes, completed work, patterns).
3. Deduplicates and removes stale entries from the Learned section.
4. Keeps the file under 50 entries.
5. Never modifies entries in the Pinned section.

/dream

/remember

Saves a pinned project memory for future sessions.

/remember <what to remember>

Automatically categorizes the memory as one of: lesson, decision, mistake, pattern, done, or preference. Saved via myk-pi-tools memory add --pinned.

Pinned memories are never auto-removed by the /dream consolidation process.

/remember always run uv lock after changing pyproject.toml
/remember the billing API requires OAuth2 client credentials flow

Session Utility Commands

/btw

Asks a quick side question without polluting the conversation history.

/btw <question>

Opens an ephemeral overlay that shows the answer. The question and answer are not added to the conversation history. The AI answers based only on existing conversation context with no tool access.

Overlay controls:

/btw what branch am I on?
/btw what was the name of that function we discussed?

/status

Shows a unified session status snapshot. Executes directly without an AI roundtrip.

/status

This command takes no arguments.

Displays:

• Async agents — count and list of running background agents with duration and task preview.
• Cron tasks — count and list of active scheduled tasks with schedule and last run time.
• Git — current branch, clean/dirty state, number of changed files, and repository name.
• Container — whether the session is running inside a container.

/status

/async-status

Shows the status of background async agents. If running agents exist, presents an interactive selector to view live streaming output.

/async-status

This command takes no arguments.

If all agents are completed, shows a static summary with completion status and duration. If running agents exist, lets you select one to view live output in a scrollable overlay.

Live output viewer controls:

/async-status

/async-kill

Kills running async agent(s) by name, ID prefix, or all at once. Without an argument, presents an interactive selection menu.

/async-kill [name|id|all]

/async-kill all
/async-kill Dream
/async-kill worker-1716000000

/dream-auto

Toggles automatic memory dreaming. When enabled, spawns a worker agent every 3 hours and on session quit to consolidate memories.

/dream-auto [on|off]

Tab completion: on, off.

Environment variable: PI_DREAM_INTERVAL_HOURS — override the dreaming interval (default: 3, range: 0.5–24).

Auto-dreaming is enabled by default. On session quit, a final dream runs as a detached process.

/dream-auto
/dream-auto on
/dream-auto off

/cron

Schedules recurring tasks within the pi session. Tasks survive /reload and /new but are terminated on pi exit.

/cron <subcommand|natural language>

Tab completion: Subcommands (add, list, list-all, remove), schedule hints (every, at), and task IDs for removal.

Schedule types:

Task types:

Note: Minimum interval is 10 seconds. Tasks are persisted to a PID-scoped file and restored after /reload.

/cron list
/cron list-all
/cron remove 1 3
/cron every 2h run /pr-review
/cron at 09:00 check for new issues

The cron_manage tool is also available for the AI to manage cron tasks programmatically with structured parameters.

cron_manage tool parameters:

/pidash

Manages the pidash web dashboard daemon. Pidash provides a browser-based UI for monitoring pi sessions, viewing conversation history, managing async agents and cron tasks, and switching models.

/pidash [subcommand]

Tab completion: start, stop, restart, status.

Environment variables:

The dashboard is accessible at http://localhost:19190 (or the configured port). It connects to pi via WebSocket and supports sending prompts from the browser, switching models, aborting operations, and viewing live streaming output.

/pidash
/pidash start
/pidash stop
/pidash restart
/pidash status

/pidiff

Manages the pidiff diff viewer daemon. Pidiff provides a browser-based UI for viewing branch diffs, file trees, and inline review comments.

/pidiff [subcommand]

Tab completion: start, stop, restart, status.

Environment variables:

Review comments published from the pidiff browser UI are automatically injected into the pi session as follow-up messages.

/pidiff
/pidiff start
/pidiff stop
/pidiff restart

/nvim-changed-files

Sends git changed files to Neovim's quickfix list. Only available when pi is running inside a Neovim terminal (the NVIM environment variable is set).

/nvim-changed-files

This command takes no arguments.

Collects all changed files (committed on the branch vs. origin/main plus uncommitted changes) and sends them to the parent Neovim instance's quickfix list via RPC. Opens the quickfix window automatically.

Note: This command is only registered when the NVIM environment variable points to a valid Neovim socket.

/nvim-changed-files

Quick Reference