본문으로 건너뛰기
cccskills
무료GitHub에 공개

loop-constraints

Load project rules before an agent starts work, then apply restrictions to file edits, tests, pushes, and merges. Check pause settings and identify actions that require human approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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.

cobusgreyling/loop-engineering
설치 방법 보기

이럴 때 유용합니다

  • Applying project rules before automated work
  • Checking protected paths before editing
  • Reviewing push and merge conditions
  • Stopping work when a pause setting is active

포함된 파일(1)

  • SKILL.md1.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

Output at start of run

Always begin with a one-line confirmation. Count each individual constraint/rule in loop-constraints.md and replace N with the actual number of active rules:

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 touched
  • loop-verifier — constraints define denylist paths the verifier must check
  • loop-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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

budget-negotiator

무료

Drafts a token budget extension request when an autonomous loop approaches its daily limit and high priority work remains. Uses logged results and remaining issues to justify the request, then pauses until a human increases the budget.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Requesting extra budget for remaining critical work
  • Summarizing daily token spending and successful actions
  • Preparing a budget request for a human maintainer
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

changelog-scan

무료

Scans merged pull requests and commits since a chosen reference, using titles, labels, milestones, and messages to categorize changes. Produces a release notes draft, highlights breaking changes and security items, and records the scan window.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Collecting changes since the previous release tag
  • Sorting updates into features, fixes, and other categories
  • Identifying breaking changes and security items
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

changelog-scan

무료

Scan recent merges, pull requests, and commits for release note material. Produce structured entries and a summary with PR references, highlighting breaking changes and security items while filtering routine dependency and bot noise.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Gathering release note material from recent changes
  • Identifying breaking changes and security items
  • Organizing changes with PR references
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

changelog-scan

무료

Scan merges and commits since the previous release to collect user-facing changes for a changelog. Produce structured entries and a summary, with explicit lists of breaking changes and security signals.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Collecting changes since the previous release
  • Organizing user-facing updates
  • Listing breaking changes and security signals
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

changelog-scan

무료

Review merged pull requests and significant commits within a release window, then organize features, fixes, breaking changes, and security signals into structured source material for drafting release notes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Collecting changes since the last release
  • Checking breaking changes and security signals
  • Preparing source material for release notes
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

ci-triage

무료

Analyze failures in CI, the automated checks run during development. Identify the failing job and step, classify the likely cause, and suggest a small fix, continued monitoring, or human review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Identifying failed jobs and steps in CI
  • Distinguishing intermittent failures from code regressions
  • Routing environment failures to a human
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

cobusgreyling의 스킬 모두 보기

이 스킬의 문제 신고