Solo-native planning workflow. Use when asked to "plan", "brainstorm", "design", "create a plan", "I want to build", or "let's build". Runs a scout, opens a planner that is interactive through approach selection, creates Solo todos, then automatically executes and reviews through Solo subagents and scratchpads.
Start a fresh Solo Pi session from the current conversation. Use when asked to hand off, continue in a clean context, or run `/handoff <new prompt>`. Writes a Solo scratchpad summary of the important current-session context, then launches an interactive Solo agent in the same project with that handoff and the new prompt.
Write clear Solo todos that workers can execute without losing architectural intent. Use when asked to "create todos", "write todos", "break into tasks", "plan todos", or create work items from a plan. Ensures each todo has outcomes, examples, constraints, and verification criteria.
Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, planning, writing, registration, and verification.
Efficiently read and analyze pi agent session JSONL files. Use when asked to "read a session", "review a session", "analyze a session", "what happened in this session", "load session", "parse session", "session history", "go through sessions", or given a .jsonl session file path.
| name | commit |
| description | Read this skill before making git commits |
Create a git commit for the current changes using Conventional Commits format with a polished, highly descriptive message. If there are commit hooks - do not skip them, it's your responsability to leave things better than they were.
<type>(<scope>): <summary>
type REQUIRED. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.git log should understand the change without looking at the diff.Signed-off-by).git status and git diff to understand the current changes (limit to argument-specified files if provided).git log -n 50 --pretty=format:%s to see commonly used scopes.git commit -m "<subject>" (and -m "<body>" if needed).