Skip to main content

Module patterns

Module patterns 

Source
Expand description

The production-loop catalogue.

Loop engineering names seven recurring loops that teams actually run. Each is just a LoopSpec constructor — sensible defaults for level, cadence, budget, and the maker/checker prompts — that you then bind to a model, tools, sandbox, and gate via crate::LoopEngine, or hand to the crate::LoopScheduler to run on its cadence.

PatternDefault cadenceLevelAction
daily_triagedaily 09:00L1report
pr_babysitterevery 10mL1comment
ci_sweeperevery 10mL2apply-patch
dependency_sweeperdaily 04:00L2open-pr
changelog_drafterdaily 18:00L1draft
post_merge_cleanupevery 6hL1report
issue_triageevery 2hL1comment

Defaults are deliberately conservative — start a loop where the table says and graduate its level as you build trust.

Functions§

catalogue
Every built-in pattern, in catalogue order. Handy for listing or for registering a whole suite with the scheduler.
changelog_drafter
Changelog Drafter — draft release notes from recent merges. Report-only; runs in the evening or on tag.
ci_sweeper
CI Sweeper — when CI is red, investigate and propose a fix. Assisted: the maker may patch inside a sandbox, but a human gates the change. Cautious and potentially expensive — budget accordingly.
daily_triage
Daily Triage — scan the project on a daily cadence and surface what needs a human’s attention. Report-only; the cheapest loop to start with.
dependency_sweeper
Dependency Sweeper — find safe dependency updates and open a PR for them. Assisted, patch-only, low cadence.
issue_triage
Issue Triage — label and route new issues, propose-only.
post_merge_cleanup
Post-Merge Cleanup — after merges, look for follow-ups: dead code, stale branches, leftover TODOs. Report-only, off-peak.
pr_babysitter
PR Babysitter — watch open pull requests and report when one needs a nudge (failing CI, requested changes, merge conflicts, gone quiet). High cadence, so keep the budget tight.