constraint-engine
par leegitw
TransportationRésumé
Learn from consequences, not instructions — generate and enforce constraints from experience.
Description
Ce que fait ce skill
Generates and enforces behavioral constraints derived from observed failures rather than predefined rules. Uses a circuit breaker pattern (CLOSED/OPEN/HALF-OPEN) to block actions that violate active constraints. Consolidates constraint generation, checking, lifecycle management, and versioning into one system.
Constraints derived from actual failures have higher adoption than manually written rules because they carry concrete consequences as evidence.
Quand l'utiliser
- Blocking a deployment when code review approval is missing
- Auto-generating a 'run tests before commit' rule after repeated CI failures
- Auditing emergency constraint overrides during incident response
- Retiring outdated constraints after 90-day review cycles
- Checking staging actions against active constraints before promotion to production
Exemple de workflow
User asks: check if I can deploy to production
- 1
Run /ce check 'deploy production' against active constraints
- 2
Identify CON-20260212-005 requires code review approval before production deployment
- 3
Determine constraint severity is CRITICAL and review approval is absent
- 4
Block the action and log to output/hooks/blocked.log
- 5
Surface the violated constraint with override instructions
[CHECK BLOCKED] deploy production — Constraint CON-20260212-005 violated: 'Always get code review approval before production deployment'. Run /ce override CON-20260212-005 "reason" to bypass with audit trail.
Installation
clawhub install leegitw/constraint-engineExécute la commande CLI, ou colle l'instruction dans Claude Code, Cursor, Codex ou l'agent de code que tu utilises.