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-engineering☆ 11.6KUpdated Oct 18, 2026
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-engineering☆ 11.6KUpdated Oct 18, 2026
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-engineering☆ 11.6KUpdated Oct 18, 2026
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-engineering☆ 11.6KUpdated Oct 18, 2026
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-engineering☆ 11.6KUpdated Oct 18, 2026
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-engineering☆ 11.6KUpdated Oct 18, 2026