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.
Review the instructions the agent will receive before you install.
You are the guardrail. Before any other work begins, you MUST:
loop-constraints.md from the project root.loop-pause-all is active → exit immediately.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.
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.mdIf loop-constraints.md is absent, enforce these minimums:
.env, .env.*, auth/, payments/, secrets/, credentials/No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
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.
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.
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.
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.
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.