Menu
Route risky patches to the right reviewer — security, backend, infra, or domain owner — by change type.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Optimize token usage and context window discipline. Reduce costs and improve response quality through smart context management.
Unified context lifecycle for FlowDeck sessions — ingest, filter, prune, protect, summarize, and persist with telemetry.
Predict affected files, modules, APIs, tests, and DB paths before changes. Returns an impact map for human review.
Map architecture, conventions, and file structure into `.codebase/`. Use when onboarding or before deep feature work.
Plan differently when the agent has low certainty — ask for clarification or narrow scope instead of pretending full understanding.
Protect critical context from pruning during compaction. Preserve active plans, safety files, pending operations, and user intent anchors.
| name | human-review-routing |
| description | Route risky patches to the right reviewer — security, backend, infra, or domain owner — by change type. |
| origin | FlowDeck |
When a patch is flagged as review-required or high-risk by the Patch Trust Score, it must be routed to the right human reviewer. This skill defines the routing logic.
| Reviewer | Triggered by |
|---|---|
| security | auth, token, password, crypto, secret, jwt, permission, rbac, xss, sql |
| backend | api, route, controller, service, database, query, migration |
| infra | docker, kubernetes, terraform, ci, cd, deploy, helm, nginx, aws, gcp |
| domain-owner | business, billing, payment, checkout, order, subscription, pricing |
| frontend | component, css, html, react, vue, ui, ux, style |
| data | schema, migration, model, index, constraint, foreign key |
| devops | pipeline, workflow, .yml, .yaml, action, cron, schedule |
security to the reviewer listsafe, route to general-reviewerProvide the files and change description to the agent to get the routing decision.
Example input:
Review route for: files=src/services/auth.ts,src/api/payment.ts change=refactor JWT validation
Output:
Route to: security, backend, domain-owner
Trust verdict: review-required
When routing a patch, include:
## Review Request
**Patch**: [brief description]
**Files**: [list]
**Trust Score**: [score] ([verdict])
**Route to**: [reviewer types]
**Reason**: [why this routing]
**Deadline**: [if blocking release]
### Key areas to check
- [specific concern 1]
- [specific concern 2]
If no appropriate reviewer is available within 24h, escalate to the tech lead. Never merge a high-risk patch without at least one human approval.