
Configure notification integrations (Telegram, Discord, Slack) via natural language
Strategic planning with optional interview workflow
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions
Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution
Configure popular MCP servers for enhanced agent capabilities
Diagnose and fix oh-my-copilot installation issues
Install or refresh oh-my-copilot for plugin, npm, and local-dev setups from the canonical setup flow
Cancel any active OMC mode (autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, team)
Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode
2-stage pipeline: trace (causal investigation) -> deep-interview (requirements crystallization) with 3-point injection
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Durable multi-goal workflow that persists plan/ledger artifacts under .omcp/ultragoal and prints Claude /goal handoff text for the active session
Socratic deep interview with mathematical ambiguity gating before explicit execution approval
Sprint planning and iteration management for Azure DevOps projects. WHEN: User wants to plan sprints, manage iterations, check team capacity, groom backlogs, or assign work to sprints. DO NOT USE FOR: Work item triage (use omc-ado-triage), PR reviews (use omc-ado-review), pipeline management, or non-ADO projects.
Automated code review for Azure DevOps pull requests where you are assigned as reviewer. WHEN: User wants automated code reviews on PRs they're assigned to, wants AI-powered PR review comments, or wants to auto-review pending PRs in Azure DevOps. DO NOT USE FOR: Manual interactive PR review (use omc-ado-review), creating PRs (use git-master agent), sprint planning (use omc-ado-sprint), or non-ADO repositories.
Multi-pass code review with security, quality, structural analysis, and validation
Critique all unpushed commits before pushing to remote
Spawn parallel specialist agents to scan the codebase and produce a prioritized improvement backlog
Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior
Deep codebase initialization with hierarchical AGENTS.md documentation
LLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model)
Generic release assistant — analyzes repo release rules, caches them in .omcp/RELEASE_RULE.md, then guides the release
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs
Autonomous evolutionary code improvement engine with tournament selection
QA cycling workflow - test, verify, fix, repeat until goal met
Quadri-model orchestration — Copilot, Claude, Codex, and Gemini each provide independent analysis, then Copilot synthesizes
Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
Extract a learned skill from the current conversation
Manage local skills - list, add, remove, search, edit, setup wizard
CLI-team runtime for claude, codex, or gemini workers in tmux panes when you need process-based parallel execution
Full autonomous execution from idea to working code
Turn a repeatable workflow from the current session into a reusable OMC skill draft
Agentic memory system for writers - track characters, relationships, scenes, and themes
N coordinated agents on shared task list using Claude Code native teams
Invoke parallel document-specialist agents for external web searches and documentation lookup
Configure HUD display options (layout, presets, display elements)
Parallel execution engine for high-throughput task completion
Self-referential loop until task completion with configurable verification reviewer
Orchestrate parallel scientist agents for comprehensive analysis with AUTO mode
Verify that a change really works before you claim completion
OMC agent catalog, available tools, team pipeline routing, commit protocol, and skills registry. Auto-loads when delegating to agents, using OMC tools, orchestrating teams, making commits, or invoking skills.
GitHub Projects (v2) board management — list items, update status, manage iterations, and add issues/PRs to projects. WHEN: User wants to manage project boards, move cards between statuses, check project progress, or assign items to iterations. DO NOT USE FOR: Issue triage (use omc-gh-triage), PR review (use omc-gh-review), initial GitHub setup (use omc-gh-setup), or ADO sprint planning (use omc-ado-sprint).
Pull request review workflow for Azure DevOps repositories. WHEN: User wants to review PRs, add reviewers, create review comments, vote on PRs, or manage PR threads in Azure DevOps. DO NOT USE FOR: Creating PRs (use git-master agent), sprint planning (use omc-ado-sprint), work item triage (use omc-ado-triage), or non-ADO repositories.
Azure DevOps work item triage — surfaces untriaged items, active work, open PRs, pipeline failures, and security alerts. WHEN: User wants to check ADO board status, triage work items, see pipeline health, review open PRs, or get a project health overview. DO NOT USE FOR: Sprint planning (use omc-ado-sprint), PR code review (use omc-ado-review), initial ADO setup (use omc-ado-setup), or non-ADO projects.
Pull request review workflow for GitHub repositories. WHEN: User wants to review PRs, read diffs, post review comments, approve or request changes on GitHub PRs. DO NOT USE FOR: Automated PR review (use omc-gh-auto-review), issue triage (use omc-gh-triage), initial GitHub setup (use omc-gh-setup), or ADO repositories (use omc-ado-review).
Configure GitHub integration for the current project. WHEN: User wants to set up GitHub integration, connect a project to GitHub, configure .omcp/config.json for GitHub, or troubleshoot GitHub connection issues. DO NOT USE FOR: Issue triage (use omc-gh-triage), project board management (use omc-gh-project), PR review (use omc-gh-review), or Azure DevOps configuration (use omc-ado-setup).
GitHub issue and PR triage — surfaces open issues, PRs needing review, failing CI, and security alerts. WHEN: User wants to check GitHub project status, triage issues, see CI health, review open PRs, or get a project health overview. DO NOT USE FOR: PR code review (use omc-gh-review), project board management (use omc-gh-project), initial GitHub setup (use omc-gh-setup), or ADO projects (use omc-ado-triage).
Hypothesis-driven experiment loop with structured notebook, git checkpoint/revert, and agent delegation
Structured visual QA verdict for screenshot-to-reference comparisons
Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
Use first for install/update routing — sends setup, doctor, or MCP requests to the correct OMC setup flow
Automated code review for GitHub pull requests where you are requested as reviewer. WHEN: User wants automated code reviews on PRs they're assigned to, wants AI-powered PR review comments, or wants to auto-review pending PRs on GitHub. DO NOT USE FOR: Manual interactive PR review (use omc-gh-review), issue triage (use omc-gh-triage), initial GitHub setup (use omc-gh-setup), or ADO repositories (use omc-ado-auto-review).
Configure Azure DevOps integration for the current project. WHEN: User wants to set up ADO integration, connect a project to Azure DevOps, configure .omcp/config.json for ADO, or troubleshoot ADO connection issues. DO NOT USE FOR: Work item triage (use omc-ado-triage), sprint planning (use omc-ado-sprint), PR review (use omc-ado-review), or Azure cloud service configuration (use azure-skills plugin).