orkl

Assesses and rates quality 0-10 with pros/cons analysis. Use when evaluating code, designs, or approaches.

Design exploration with parallel agents. Use when brainstorming ideas, exploring solutions, or comparing alternatives.

Creates commits with conventional format and validation. Use when committing changes or generating commit messages.

Configures OrchestKit settings. Use when customizing MCP servers, plugin options, or preferences.

Creates GitHub pull requests with validation. Use when opening PRs or submitting code for review.

OrchestKit doctor for health diagnostics. Use when running checks on plugin health, diagnosing problems, or troubleshooting issues.

explore — Deep codebase exploration with parallel agents. Use when exploring a repo, discovering architecture, finding files, or analyzing design patterns.

Manages OrchestKit feedback system. Use when providing feedback or viewing usage analytics.

Fixes GitHub issues with parallel analysis. Use to debug errors, resolve regressions, fix bugs, or triage issues.

Complete git workflow patterns including GitHub Flow branching, atomic commits with interactive staging, merge and rebase strategies, and recovery operations using reflog. Essential patterns for clean history. Use when managing branches, defining branching strategy, or recovering git history.

OrchestKit skill directory. Use when you want to see available skills or need help.

Full-power feature implementation with parallel subagents. Use when implementing, building, or creating features.

Auto-updates GitHub issues with commit progress. Use when starting work on an issue, tracking progress during implementation, or completing work with a PR.

Read-side memory operations: search, recall, load, sync, history, visualize. Use when searching past decisions, loading session context, or viewing the knowledge graph.

Visualize planned changes before implementation. Use when reviewing plans, comparing before/after architecture, assessing risk, or analyzing execution order and impact.

Stores decisions and patterns in knowledge graph. Use when saving patterns, remembering outcomes, or recording decisions.

PR review with parallel specialized agents. Use when reviewing pull requests or code.

Assess platform upgrade readiness for Claude model and CC version changes. Use when evaluating upgrades.

Comprehensive verification with parallel test agents. Use when verifying implementations or validating changes.

Coordinates multiple Claude instances across worktrees. Use when managing parallel development.