mcpField
C
coding-router

coding-router

github.com/kesslerioAgent workflows10144 installsUpdated 30w ago
Repository

About coding-router

coding-router is a compatibility skill that routes coding-related requests to planning, review, or implementation workflows. It requires explicit APPROVE before file changes or other implementation actions and avoids defaulting to permission-bypass flags.

Key features

  1. 01Route planning and scoping requests
  2. 02Require APPROVE before implementation
  3. 03Dispatch to coding-agent behavior
  4. 04Route plan and review aliases
  5. 05Emit runtime status events

Use cases

  1. 01Plan a non-trivial implementation before editing
  2. 02Route a request through plan review
  3. 03Run a coding task after explicit approval

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/kesslerio/coding-agent-openclaw-skill --skill coding-router

After installing, type/coding-routerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

.gitignore
AGENTS.md
CLAUDE.md
CONTRIBUTING.md
README.md
TODOS.md
THEORY.MD
VERSION
.github/
pull_request_template.md
.github/ISSUE_TEMPLATE/
bug_report.yml
feature_request.yml
config.yml
docs_issue.yml
task_chore.yml
.github/workflows/
pr-policy.yml
wrapper-smoke.yml
reusable-pr-checks.yml
references/
STANDARDS.md
acp-troubleshooting.md
WORKFLOW.md
frontend-design.md
examples.md
claude-code.md
codex-cli.md
gemini-cli.md
lobster-workflows.md
reviews.md
quick-reference.md
references/templates/
plan-review-system-prompt.txt
plan-system-prompt.txt

Details

From the project README

Coding Router Skill 💻

This file exists for backward compatibility with single-entry skill setups (for example /coding). Canonical sibling skills live at:

  • skills/plan-issue/SKILL.md
  • skills/coding-agent/SKILL.md

Routing Rules

  1. If user asks to plan/scope/estimate/design, follow plan-issue behavior.
  2. For non-trivial implementation requests, produce a plan first and wait for exact APPROVE before any writes.
  3. Only after APPROVE, follow coding-agent behavior with ACP-aware execution routing and CLI fallback.

Command Routing (Channel Aliases)

When invoked via channel aliases:

  • /coding → use this compatibility skill as router.
  • /plan → route directly to plan-issue behavior.
  • /plan-review → route to plan review flow using scripts/plan-review.
  • /plan-review-live → route to interactive plan review checkpoints using scripts/plan-review-live (Lobster in-repo workflow first, legacy fallback).
  • /review_pr → route to review flow using references/reviews.md.

Runtime Status Contract

When wrappers are used for planning/review:

  • Emit RUN_EVENT start at run start.
  • If the run exceeds 30s, emit RUN_EVENT heartbeat every 20s.
  • If interrupted or timed out, emit RUN_EVENT interrupted immediately with exit code.
  • On non-interruption failure, emit RUN_EVENT failed.
  • On success, emit RUN_EVENT done.

Known ACP Runtime Limitation

Issue #43 (upstream) may affect spawned ACP run observability and browser relay profile alias mapping. Use repo-side mitigations and bounded fallback guidance in:

  • references/acp-troubleshooting.md

Non-Negotiable Gates

  1. Never write files, install packages, commit, or open PRs before explicit APPROVE.
  2. Never default to bypass flags (--yolo, --dangerously-skip-permissions).
  3. Use bypass flags only when the user explicitly asks to bypass approvals.

Comments

Markdown supported