loop-engineering

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.

Scan merged PRs and commits since a given reference, extract titles, labels, types, and signals. Produces structured input for release notes drafting.

Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.

Scan package manifests and lockfiles for outdated and vulnerable dependencies. Classify by severity and update type.

Scan open issues and discussions, deduplicate, prioritize, and propose labels. Provides a clean actionable queue.

Scan recent merges to main for tech debt, TODOs, debug code, and small cleanup opportunities. Produces a prioritized fix list.

Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.

Triage recent changes, CI failures, issues, and conversations. Produces a concise, actionable findings report suitable for a loop to consume. Writes structured output to a state file or issue tracker.

Verify goal completion.

Scan open issues and discussions. Dedupe, prioritize, and propose labels. Updates issue-triage-state.md. L1 propose-only — never auto-label or close.

Check token budget and run-log spend before and after a loop run. Enforces early exit when over budget or when there is no actionable work.

Scan recent merges/PRs/commits for release note content. Structured output for drafter.

Turn changelog-scan output into polished, categorized release notes draft. Propose only.

Scan recent merges and commits since last release for changelog content.

Generate categorized release notes draft from scan data. Human must approve before publish.

Scan recent merges to main (and noteworthy direct commits) since a given window (last tag or date in state). Extract titles, labels, types, linked issues, and signals for breaking changes or security. Produces structured input for a release notes drafter. Use in changelog-drafter loops.

Takes a structured list of changes from changelog-scan and produces a clean, categorized, user-facing release notes draft. Follows project voice and conventions. Never publishes — only proposes a draft file or section.

Independent checker for release note drafts. Reviews accuracy against the changelog-scan data, tone, completeness, and flags breaking/security items. Use after draft-release-notes. Never let the drafter verify itself.

Parse CI failures, identify failing job/step, classify as flake, regression, env, or config. Use in CI sweeper loops before any fix attempt.

Scan package manifests and lockfiles for outdated packages and known CVEs. Groups updates by risk (patch, minor, major). Use in dependency sweeper loops.

Scan recent merges to main for follow-up cleanup: TODOs, deprecations, broken doc links, stale flags. Use in post-merge cleanup loops.

Triage open pull requests for CI status, review comments, and merge readiness. Use in PR babysitter loops. Respects project review norms and required checks.

Triage recent changes, CI failures, issues, and conversations. Produces a concise, actionable findings report suitable for a loop to consume. Writes structured output to a state file or Linear board.

Independent verification agent for loop-produced changes. Finds reasons to reject. Runs tests. Confirms diff scope. Use after minimal-fix or any implementer sub-agent — never in the same role as the implementer.

Produce the smallest possible code change that fixes a specific, well-scoped issue (CI failure, reviewer comment, typo). Use only when the fix target is explicit. Never refactor unrelated code.