change-router

Classifies code changes into L0-L3 levels and selects the minimal execution workflow.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/shengmingzhishu/LeeCommonSkills --skill change-router-shengmingzhishu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-router
Source: https://github.com/shengmingzhishu/LeeCommonSkills/tree/main/.trae/skills/shared/change-router
Command: npx skills add https://github.com/shengmingzhishu/LeeCommonSkills --skill change-router-shengmingzhishu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing a bug fix, feature change, new module, or system refactor, teams often either over-engineer simple fixes or under-plan risky changes. This Skill triages every change request into an L0-L3 severity level and routes it to the smallest sufficient workflow, preventing skipped impact analysis on APIs, data, security, and cross-end concerns. ## Core Features & Use Cases - Change Triage: Evaluates public contracts, data impact, cross-end effects, security, module count, compatibility, and rollback risk using a structured checklist. - Level-Based Routing: Maps L0-L3 levels to concrete execution paths, loading only the skills needed for that level (debugging, impact analysis, API contracts, DB migration, security audit, CI/CD). - Escalation Conditions: Outputs explicit upgrade triggers so a change that grows in scope must move to a higher-level process. - Use Case: A developer asked to "just add a field to an API" runs the triage, discovers the change touches a public contract and database schema, and gets routed to an L2 path with API contract and test review instead of a quick edit. ## Quick Start Ask the AI to triage your change request, for example: "Route this change: add a new status field to the order API and update the frontend list page."

Frequently Asked Questions about change-router

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

FAQPage Schema
How do I decide which workflow to follow for a code change?▼

Run a change triage that checks public contracts, data, cross-end impact, security, module count, compatibility, and rollback risk. The result maps to an L0-L3 level, and each level defines the exact stages, artifacts, and verification steps to follow.

What is change triage in a software development workflow?▼

Change triage is a pre-implementation assessment that classifies a request by risk and scope before coding starts. It ensures simple fixes stay lightweight while risky changes get design, contract, migration, and security review.

When should a small bug fix be escalated to a full design process?▼

Escalate when the fix touches a public API contract, shared data schema, multiple modules, security-sensitive code, or lacks a safe rollback path. The triage outputs explicit upgrade conditions that force a higher-level process when triggered.

Does change routing skip impact analysis for simple requests?▼

No. The routing rules explicitly forbid skipping API, data, security, and cross-end impact checks just because a request sounds simple. Every change passes the same triage checklist; only the downstream workflow varies by level.

Can the change router implement the code after triage?▼

No. The skill only routes: it outputs the level, path, required artifacts, and verification method. Implementation is delegated to level-appropriate downstream skills such as debugging, API contract, testing, or database migration skills.