القائمة
Manage dev environment orchestration with process-compose. Use for devstack init, worktrees, starting/stopping services, DEVSTACK.md, bin/dev, or 'create process-compose'.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review recently changed code for reuse, simplification, efficiency, and consistency cleanups, then apply the fixes. Quality only — doesn't hunt for bugs. Triggers on 'simplify', 'clean this up', 'simplify this diff'.
Rigorous code review of completed implementation before committing. Use for features, refactors, and critical-path changes — not trivial changes (this is expensive).
Post-implementation checklist — docs, code quality, conventions, visual verification, issue hygiene. Triggers on 'finalize', 'ready to merge', 'preflight check', 'wrap this up', 'final review'.
Run the full pre-merge pipeline and create a PR. Triggers on 'ship', 'ship it', 'ready to ship', 'prep for PR', 'create PR', 'ready to merge'.
Spin up an isolated git worktree in its own tmux session — coding agent in one window, dev stack in another, git UI in a third — with the agent briefed and already working. Use for spinning up a worktree, starting a feature/branch/task in isolation, handing work to a fresh agent (Claude/Codex), or setting up an isolated tmux dev session.
Read, send input to, or spawn other tmux panes, windows, and sessions - including agents (Claude Code, Codex), REPLs, and TUIs running in them. Use when the user references another pane, window, or agent.
| name | devstack |
| description | Manage dev environment orchestration with process-compose. Use for devstack init, worktrees, starting/stopping services, DEVSTACK.md, bin/dev, or 'create process-compose'. |
Manages dev environments using process-compose for headless process orchestration with health checks, dependency ordering, and a TUI. Works for both humans and AI agents.
Status: Work in progress (March 2026). If you encounter unexpected issues controlling the running stack (client commands failing, connection refused, socket errors), surface these to the user immediately rather than silently working around them. The user maintains this skill and needs feedback to improve it.
Check context to determine which mode to use:
Init mode — the project does NOT have a DEVSTACK.md yet, or the user
explicitly asks to set up devstack:
references/init-reference.mdDaily mode — the project HAS a DEVSTACK.md, and the user wants to
create worktrees, start/stop services, or manage the dev environment:
DEVSTACK.md in the project root and follow its instructionsreferences/daily-reference.mdIf DEVSTACK.md exists, these are the standard commands:
| Task | Command |
|---|---|
| Start (human, TUI) | bin/dev |
| Start (agent, headless) | bin/dev -D |
| Stop | bin/dev stop |
| Status (table) | bin/dev status |
| Status (JSON) | bin/dev status --json |
| Logs | bin/dev logs <service> |
| Restart service | bin/dev restart <service> |
| Wait for healthy | bin/dev status (poll until all services show Ready) |
Always read DEVSTACK.md for project-specific details — the commands above
are conventions, not guarantees.