Menu
Assign a confidence and risk rating to every AI-generated change. Returns safe, review-required, or high-risk verdict with specific signals.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | patch-trust-score |
| description | Assign a confidence and risk rating to every AI-generated change. Returns safe, review-required, or high-risk verdict with specific signals. |
| origin | FlowDeck |
Every AI-generated patch gets a trust score before it is applied. The score gates how the change is handled: auto-apply, flag for review, or block and escalate.
| Score | Verdict | Action |
|---|---|---|
| 80–100 | safe | Auto-apply in guarded mode |
| 40–79 | review-required | Inline warning + human ACK |
| 0–39 | high-risk | Block auto-apply, route to reviewer |
| Signal | Deduction |
|---|---|
| File has prior failure history | −20 |
| Edit contains auth/crypto/payment keywords | −8 per keyword (max −30) |
| File in arch-constrained zone | −20 |
| No test coverage for file | −10 |
.codebase/FAILURES.json for prior failures on this file
b. Scan the patch content for high-risk keywords
c. Check .codebase/CONSTRAINTS.md for boundary violationsThe patch-trust hook runs automatically on every write and edit tool call. The score is logged to stdout and appended to .codebase/DECISIONS.jsonl.
For manual scoring, use the patch-trust-score skill with a file path and change description.