Session basics
Set up a session, select a model, inspect profile, usage, or orchestration state, and decide whether large work needs a new session (/new).
Short commands, predictable behaviour
Slash commands package policy and flow, with one inspector for diffs, commands, safety and context.
Project profile
Apply a profile directly or use a deterministic selector for the profile and tech stack. Output stays compact and does not require model interpretation.
Assigning work
Since 1.9.0 there is no /workflow, /task or task contract: say what you need in plain language; the guard checks every tool call.
Git handoff
There is no /git namespace. Commits and PRs are ordinary requests; pushes, GitHub writes and broad staging such as git add -A require confirmation.
New sessions
Start a clean session when the current context is heavy or belongs to different work (/fresh was retired in 1.9.0).
MCP
Inspect and configure tool servers with the core, popular, or design presets.
Subagents
Inspect runtime health, model routing, background runs, and cost. Daily work remains solo-first; subagents are reserved for independent scouting, planning, or review lanes.
Product visibility
Inspect runtime decisions
These commands read deterministic state without asking a model to interpret it. They are optional in the daily workflow.
/task-preflight --json Review current repository stateInspect intent, risk, scope, runtime, solver route, phases, tool and helper recommendations, backend, approvals, and blockers before starting.
/piagent-statusThe session's profile, guard, runtime and model. It changes no file, reruns no check and starts no model turn.
/piagent-inspectorOne menu for summary, files, commands, security, context, and toggle. A four-row panel appears automatically just above the native footer: green is healthy, yellow needs attention, and red marks failures, safety warnings, or context at 80% and above. The command reads local state without calling a model.
/usage efficiencyInspect context and tool utilization, verification, repair, retries, and helper usage. Runtime values that cannot be measured stay null.
/piagent-orchestrationInspect the solo-first policy, read-only roles, reviewer or Oracle recommendations, owned budgets, and the one-writer invariant.
Sourced diffs, no token estimates.
The footer panel uses the files observed in the session for fast updates; the files view computes the exact snapshot delta and marks mixed-working-tree when a turn touches a file that was already dirty. Pi exposes model usage by turn and session, so per-built-in-tool tokens remain unavailable.
Optional skills and packages
Audit test quality, run experiment loops
/skill:test-audit audit the tests of the billing moduleThe test-audit skill ships with Piagent: it stops new tests that protect no behavior and finds duplicated tests, tests tied to the implementation, and code that exists only for tests. The agent uses it when writing or changing tests; run the command to sweep a whole area.
git switch -c experiment/test-speedIf you add a package with an automatic experiment loop (run_experiment, log_experiment): the guard checks each experiment command like any shell command, and lets the loop run only on an experiment/ branch or a worktree of its own, started with nothing uncommitted, because every dropped idea erases all uncommitted changes.