coding-router
Compatibility entry skill for plan-first coding work in OpenClaw.
Best use case
coding-router is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Compatibility entry skill for plan-first coding work in OpenClaw.
Teams using coding-router should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
How coding-router Compares
| Feature / Agent | coding-router | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Compatibility entry skill for plan-first coding work in OpenClaw.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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.
Related Skills
coding-agent
Implementation/review workflow for approved plans. Route ACP-first, then CLI fallback. Use after explicit APPROVE.
plan-issue
Plan-only workflow for issue/repo changes. Use when user asks to plan, scope, estimate, or design.
agentic-coding
Expert agentic coding methodologies including autonomous AI development, multi-agent systems, and self-improving code generation
frappe-router
Route to the appropriate Frappe skill based on task type. Use as the entry point when working on Frappe projects to determine which specialized skill to apply.
typescript-coding-standards
TypeScript coding standards covering strict type system, advanced types, decorators, generics, and best practices for type-safe applications. Use for TypeScript projects requiring robust type safety and maintainable code.
swift-coding-standards
Master Swift coding standards with Apple's guidelines, protocol-oriented design, and modern concurrency patterns
rust-coding-standards
Master Rust's ownership system, type safety, and zero-cost abstractions for building safe, concurrent, and performant systems. Covers borrowing, lifetimes, traits, error handling, async/await, and testing patterns.
python-coding-standards
Python coding standards following PEP 8, type hints, testing best practices, and modern Python patterns. Use for Python projects requiring clean, maintainable, production-ready code with comprehensive testing.
kotlin-coding-standards
Master Kotlin coding standards with null safety, coroutines, and idiomatic patterns. Use when developing JVM/Android applications requiring type-safe async programming.
javascript-coding-standards
JavaScript/ES6+ coding standards following Airbnb guidelines, modern patterns, React best practices, and comprehensive Jest testing. Use for JavaScript projects requiring clean, maintainable, production-ready code with modern tooling.
go-coding-standards
Go coding standards following idiomatic Go patterns, error handling, concurrency best practices, and modern Go tooling. Use for Go projects requiring clean, efficient, production-ready code with comprehensive testing.
coding-standards
Comprehensive coding standards and best practices for maintainable, consistent software development across multiple languages and paradigms