agent-routing

Route multi-agent git-review tasks through role and model tier pipelines.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/monktui/git-review --skill agent-routing-monktui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-routing
Source: https://github.com/monktui/git-review/tree/main/.claude/skills/agent-routing
Command: npx skills add https://github.com/monktui/git-review --skill agent-routing-monktui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of coordinating a multi-agent workflow by defining which agent should handle which task and which model tier to use, reducing delays and inconsistent outputs.

Core Features & Use Cases

  • Agent pipeline orchestration: Prescribes an ordered workflow from requirements gathering through planning, implementation delegation, review, QA, and documentation updates.
  • Role-based delegation rules: Clarifies when to use junior-coder (scaffolding/boilerplate), coder (standard logic + tests), or senior-coder (cross-module/performance/complex refactors).
  • Model routing & conflict resolution: Enforces model tier assignments and states that agent specifications take precedence over routing suggestions.
  • Commit safety guardrails: Requires tech-lead approval after each implementation step and centralizes when the orchestrator commits.

Quick Start

Assign a task to the orchestrator and apply the agent-routing rules to select the correct agent tier, run the pipeline in order, and pause for tech-lead review before committing.

Frequently Asked Questions about agent-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate multi-agent workflows for code review?

Multi-agent workflow orchestration for code review routes tasks through a defined pipeline of roles and model tiers, spanning requirements, implementation, QA, and documentation. It applies deterministic role selection rules to coordinate agents and reduce inconsistent outputs.

What are the best model routing rules for delegating coding tasks?

Model routing for coding tasks enforces tier assignments based on complexity: junior-coder for scaffolding, coder for standard logic and tests, and senior-coder for cross-module refactors. Agent specifications always take precedence over general routing suggestions during delegation.

How do commit gating and tech-lead approval checkpoints work in an agent pipeline?

Commit gating in an agent pipeline requires tech-lead approval after each implementation step before the orchestrator commits changes. This safety guardrail centralizes the commit process, ensuring iterative implementation is reviewed and authorized before finalizing code.

Can I use deterministic role selection to manage iterative implementation delegation?

Yes, deterministic role selection manages iterative implementation delegation by assigning specific agent tiers to ordered pipeline phases. It clarifies exactly when to use junior-coder, coder, or senior-coder roles based on task requirements, ensuring structured delegation.

When should agent specifications override model routing suggestions?

Agent specifications should override model routing suggestions whenever there is a conflict in task assignment. The delegation framework relies on authoritative agent specifications to enforce model tier assignments, ensuring the correct agent handles the specific pipeline phase.