🛡️
AI EngineeringJavaScript

Loop Constraints

by cobusgreyling

Loop Constraints is an AI Engineering skill for Claude Code, published by cobusgreyling in loop-engineering.

10.4K stars1.4K forkson cobusgreyling/loop-engineeringAdded 2026/08/15+1% in starsRepository updated 2026/08/15
agentic-aiai-agentsai-codinganthropicautomationclaudeclaude-codecodexcoding-agentsdevops-automationdevtoolsgithub-actionsgrokllmloop-engineeringmcpprompt-engineering
Install in seconds
Install Loop Constraints
Copy Loop Constraints into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/cobusgreyling/loop-engineering/tree/main/skills/loop-constraints ~/.claude/skills/loop-constraints

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/cobusgreyling/loop-engineering.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/loop-constraints/SKILL.md in cobusgreyling/loop-engineering
Installs to
~/.claude/skills/loop-constraints
Collection
One of 23 skills cataloged from this repository
Category
AI Engineering2451 skills

What Loop Constraints does

Loop Constraints reads loop-constraints.md at the start of every run and enforces all rules before triage or actions. Use it to apply binding guardrails such as denylist paths, push/merge checks, and test requirements.

Loop Constraints is cataloged under AI Engineering on DirSkills. Loop Constraints comes from a repository tagged agentic-ai, ai-agents, ai-coding, anthropic and automation.

Documentation

README

Loop Constraints Enforcer

You are the guardrail. Before any other work begins, you MUST:

  1. Read loop-constraints.md from the project root.
  2. Load every rule into your working memory.
  3. Check if loop-pause-all is active → exit immediately.
  4. 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.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Loop Constraints

  • What else does cobusgreyling publish alongside Loop Constraints?

    Loop Constraints is one of 23 skills that DirSkills catalogs from cobusgreyling/loop-engineering, the repository it ships in. Its siblings there include Budget Negotiator, CI Triage and CI Triage. Each one is a separate skill with its own page in this directory, installs the same way Loop Constraints does, and is maintained by cobusgreyling in that same repository. The rest of the collection is listed on the cobusgreyling/loop-engineering page.

  • How does Loop Constraints compare to other AI Engineering skills?

    Loop Constraints ranks #387 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Loop Constraints against them. Open each page to compare what they document and how they install.

More from cobusgreyling/loop-engineering

Loop Constraints is one of 23 skills cataloged on DirSkills from cobusgreyling/loop-engineering.

See all 23 skills
💰
2w ago

Budget Negotiator

Budget Negotiator enables an L3 autonomous loop to request a token budget increase when near its cap and high-priority work remains. It calculates ROI from run logs and escalates a tagged request for human approval.
AI Engineering
10.4K1.4K
🩺
2w ago

CI Triage

CI Triage classifies failing CI checks into clear regressions, infra flakes, security-test failures, and non-deterministic failures, then updates ci-sweeper-state.md with suggested next actions and attempt counts. Use it when you need to decide whether to auto-fix, retry, or escalate each CI failure.
DevOps
10.4K1.4K
🔍
2w ago

CI Triage

CI Triage parses CI failures, identifies the failing job and step, and classifies each failure as flake, regression, env, or config to guide next actions. Use it before attempting any fix to decide whether to minimal-fix, watch, or escalate.
DevOps
10.4K1.4K
📝
2w ago

Changelog Scan

Changelog Scan scans merged PRs and commits since a given reference, extracting titles, labels, types, and signals. It produces structured input for release notes drafting.
DevOps
10.4K1.4K
📋
2w ago

Changelog Scan

Changelog Scan reviews recent merges, PRs, and commits to extract release note content, returning structured per-item blocks and a scan summary. It surfaces breaking and security changes explicitly and ignores dependency and bot noise unless security-related.
DevOps
10.4K1.4K
📋
2w ago

Changelog Scan

Changelog Scan analyzes recent merges and commits since the last release to extract user-facing changes, breaking changes, and security signals. Use it to generate structured changelog entries for release notes.
DevOps
10.4K1.4K