メニュー
Use when managing Solo projects, dev processes, or when the user asks to use Solo CLI, start or inspect dev servers through Solo, or check Solo status.
Use after fixing or investigating a hard-earned bug that took significant debugging, crossed multiple files or systems, had misleading symptoms, or revealed durable system behavior worth preserving in docs/knowledge/learnings.
Systematically upgrade project dependencies. Use for Composer, npm, bun, pnpm, yarn, lockfile updates, security updates, Laravel/PHP upgrades, React/JavaScript upgrades, framework bumps, package modernization, or dependency cleanup.
Use when answering questions about a project feature, documenting existing functionality, investigating product behavior, or maintaining docs/knowledge feature packs, glossary terms, aliases, key files, and feature history.
Stress-test and challenge ideas before building. Use when the user wants to think through code architecture, UX/UI, or product direction before implementation.
Find high-leverage product opportunities. Use when the user wants product strategy, asks what would make something 10x better, or wants to decide what to build next.
Run project checks from repo-root `CHECKLIST.md` and fix task-related failures, including skipped tests. Use when the user asks to run checks, lint and fix, or verify code quality.
| name | solo-cli |
| description | Use when managing Solo projects, dev processes, or when the user asks to use Solo CLI, start or inspect dev servers through Solo, or check Solo status. |
Use solo as the first choice for Solo-managed projects and dev processes. For complete syntax and current flags, run solo --help or solo <command> --help.
solo doctor or solo status when connection or discovery is uncertain.solo projects list --json to get current project IDs.--project-id for project-scoped commands and --json when parsing output.solo processes list before process-specific actions.solo doctor
solo projects list --json
solo projects get 2 --json
solo processes list --project-id 2 --json
solo commands start-all --project-id 2
solo commands stop-all --project-id 2
solo commands restart-all --project-id 2
solo processes restart <process-id>
# awraq-project at /Users/muhammed/PhpstormProjects/awraq-project
solo processes list --project-id 2 --json
solo commands start-all --project-id 2
# harium-project at /Users/muhammed/PhpstormProjects/harium-project
solo processes list --project-id 1 --json
solo commands start-all --project-id 1
Verify IDs with solo projects list --json; do not assume they are stable forever.