Groom rough software ideas into source-backed implementation specs with original intent, capability discovery, tracker hierarchy, QA, Gherkin, and Notion documentation projection.
Append environment variables to ~/.zshenv on bigmac, genomesbox, and the Mac laptop in one step. Use when the user pastes `KEY=value` pairs and asks to add them to zshenv, or when setting secrets that need to be available on all three hosts. ssh aliases `bigmac`, `genomesbox`, and `mac` are already configured where needed.
Commit all local changes in logical groups until the repository is clean. Use when the user asks to commit everything, make all needed commits, or cleanly commit the full worktree without pushing.
Help users operate the published Composio CLI to find the right tool, connect accounts, inspect schemas, execute tools, subscribe to trigger events with `composio listen`, script workflows with `composio run`, and call authenticated app APIs with `composio proxy`. Use when the user asks how to do something with `composio`, wants to run a known tool slug, needs to discover a slug with `composio search`, fix a missing connection with `composio link`, inspect tool inputs with `--get-schema` or `--dry-run`, troubleshoot top-level CLI flows, or explicitly needs `composio dev` guidance.
Use when the user wants to work a LOS Jira ticket or non-trivial LOS task in a dedicated fast worktree, especially when they mention /workon, /orchestrate, fast worktree, use a worktree, or parallel agents.
Use when working or resuming LOS Jira implementation in a fast worktree with minimal chat output, especially after noisy /workon loops, repeated stack setup, test polling, or context/token burn.
Orchestrated GitHub PR review skill. Use when the user provides a PR link or asks for a senior, blocker-focused pull request review with Jira acceptance, tests, docs, security, architecture, memory, and copy/paste GitHub markdown comments.
Use when LOS implementation needs multi-agent fan-out, several work units, risk-routed quality holdouts, full PR lifecycle management, pre-commit blocked CI fallback, or mandatory Copilot comment resolution with chat kept to receipt-backed milestones only. The orchestrator plans, decomposes, dispatches worker and explorer subagents, verifies returns, and routes gates; evidence lives in the Agentic OS work item and durable PR/Jira summaries. NOT for single-agent quiet edits; use los-quiet-workon. NOT for worktree or stack setup alone; use los-fast-workon. Triggers include "orchestrate this ticket quietly", "fan this out with subagents", resuming noisy orchestration, or long-running LOS work that burns context with status chatter.