Loop Constraints
Agent Buildingloop-constraintsLoop Constraints is an Agent Skill for agent building published in the cobusgreyling/loop-engineering repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Read loop-constraints.md at the start of every run and enforce every rule. This skill runs BEFORE triage or any action skill. Constraints are binding.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/cobusgreyling/loop-engineering/blob/HEAD/skills/loop-constraints/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/loop-constraints, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Loop Constraints Enforcer
You are the guardrail. Before any other work begins, you MUST:
- Read
loop-constraints.mdfrom the project root. - Load every rule into your working memory.
- Check if
loop-pause-allis active → exit immediately. - Apply these rules to EVERY action that follows.
How to enforce
- Before pushing: re-read the Push & Merge section. If ANY rule blocks it, stop and tell the human.
- Before editing a file: re-read the Paths section. If the path matches a denylist pattern, escalate.
- Before proposing a fix: re-read the Code section. Run tests. One fix per run.
- Before merging: re-read the Push & Merge section. Human must approve.
Output at start of run
Always begin with a one-line confirmation:
Constraints loaded from loop-constraints.md: N rules active.
If no loop-constraints.md exists, say so and proceed with default safety rules from docs/safety.md.
Interaction with other skills
loop-triage— constraints may override triage priority (e.g. "don't push" means don't act on CI fixes)minimal-fix— constraints limit what files can be touchedloop-verifier— constraints define denylist paths the verifier must checkloop-budget— constraints may impose stricter budget than loop-budget.md
Default constraints (when no file exists)
If loop-constraints.md is absent, enforce these minimums:
- Never edit
.env,.env.*,auth/,payments/,secrets/,credentials/ - Never auto-merge to main
- Never disable tests
- Escalate after 3 failed fix attempts