القائمة
Autonomous error detection and repair pipeline. Runs parallel to Build Loop. Capture → Confirm → Investigate → Fix → Prove → Light Council → Deliver or Escalate.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Orchestration skill: chains the full ADLC Build Loop. PRD → Brief → Council → Scaffold → Codegen → LDD → TDD → Council → PR. Use when implementing a new feature end-to-end.
Generate a bounded, schema-valid goal prompt from one validated Build Brief task for zero-context external execution.
Applicability-aware Definition of Done checklist. Core checks apply to every task; overlay checks activate only when the applicability manifest says the surface exists. Binary verification — pass or fail. Triggers at Phase 4 completion and Phase 5 entry.
Score whether each task is specific enough for autonomous, one-shot, production-ready execution.
Reviews code changes for understanding, blast radius, state, secrets, assumptions, and explainability. Produces a blocking comprehension artifact when implications are unclear.
Resolve ambiguous triage outcomes in the middle confidence band.
| name | fix-loop |
| description | Autonomous error detection and repair pipeline. Runs parallel to Build Loop. Capture → Confirm → Investigate → Fix → Prove → Light Council → Deliver or Escalate. |
The Fix Loop runs in parallel with the Build Loop. It watches production for errors and autonomously repairs them. The Architect reviews fixes, not triages bugs.
Capture → Confirm → Investigate → Fix → Prove → [LIGHT COUNCIL] → Deliver PR
↑ |
└── Retry (max 3) ──────────────┘
|
Escalate (if 3 fails) ←─────────┘
Monitor for errors with full context:
| Source | What to Capture |
|---|---|
| Error monitoring | Exceptions: type, message, stack trace, correlation ID |
| Health checks | Degraded/failed endpoints with response details |
| Test regressions | Tests that previously passed now failing |
| Performance anomalies | Latency spikes, throughput drops with timing data |
| Security alerts | Dependency vulnerabilities, suspicious access patterns |
Domain adaptation:
Filter noise from signal:
Root cause analysis with codebase context:
git blame and recent changes for related codeWrite the fix in isolation:
If fix doesn't pass: Retry with enriched context (failure reason from previous attempt). Max 3 retries.
Evidence package:
3 personas review (not full 6 — this is a fix, not a feature):
| Persona | Focus |
|---|---|
| Skeptic | Does this fix the root cause, or just the symptom? |
| Operator | Is the fix safe to deploy? Rollback plan? |
| Security Auditor | Does the fix introduce new security issues? |
Verdicts: APPROVED / REVISION REQUIRED (retry) / ESCALATE (human needed)
PR with:
If 3 fix attempts fail, create detailed issue with:
adlc:
fix_loop:
enabled: true
confirmation_threshold: 5 # errors in window = confirmed
confirmation_window_hours: 1
max_fix_attempts: 3
auto_escalate: true
council_weight: light # skeptic + operator + security_auditor
security_auto_elevate: true # security fixes → Critical risk tier