Loops: recurring engineering work, handed to an agent.

If you have Dependabot or Renovate on, you know the pile. A stack of updates lands and they are not equally important: some are boring patch bumps, some are security fixes, some look small until you realize they touch a risky part of the stack.

This loop works the pile so you don't merge blind: it clears the safe bumps, fixes what's broken, and ranks the rest by risk.

Trigger

Recurring sweep over open Dependabot PRs

Goal

Clear the safe updates, fix what's broken, and rank the rest by risk

Artifact

Safe bumps merged · failing CI diagnosed and fixed · risky bumps left with a written assessment · a Slack digest of everything it did

Handoff

You review what it merged and make the call on anything risky

It merges the boring, safe bumps and pushes obvious CI fixes. The risky ones it leaves untouched with a written assessment: major bumps, breaking changes, anything uncertain. Your attention goes to the calls that actually need a human.

You merge a PR. Did it actually ship? Most teams can't answer that without digging through releases and compare views by hand. And the open PRs you're waiting on: are their deploy gates finally clear, or still blocked on something upstream?

This loop answers both, read-only: what shipped, whether your merged work made it into a release, and which open-PR gates have cleared.

Trigger

Recurring sweep, typically each morning (default window: past 24 hours)

Goal

Confirm what shipped and whether open-PR deploy gates have cleared

Artifact

A Shipping Status report: releases in the window · your shipped work · merged-PR → first-release table · open-PR gate status · follow-up questions

Handoff

You decide which follow-ups to act on

It takes no write actions: no merges, no label changes, no messages. Every suggestion comes back as a question you approve later. A review surface, not an actor.

The problem with docs isn't that nobody knows they matter. It's that implementation moves, releases ship, setup steps change, and the docs quietly fall behind because nobody is explicitly watching for it.

This loop watches for it: it reads your code and your docs, finds where they've diverged, fixes the clear low-risk drift itself, and flags the rest.

Trigger

Recurring sweep over recent git history and the working tree

Goal

Find where code and docs have diverged, and close the gap where it's safe

Artifact

Clear low-risk docs fixes committed and pushed · ambiguous gaps reported with exact files and a suggested update

Handoff

You decide on the ambiguous gaps it didn't touch

It only auto-fixes drift that's clear and low risk: docs-only, verified, conventional commit. Anything ambiguous it leaves alone and reports, with the exact source and stale docs, for you to decide.

I have a recurring team meeting, and before it I want to reconstruct what actually changed since the last one. Not status theater. Not a fake AI standup. Just a clean prep artifact so when it's my turn I can talk clearly about what moved.

Trigger

The meeting cadence

Goal

Reconstruct the week across the systems where work actually happened

Sources

Obsidian notes · Linear issues · Slack threads

Artifact

What changed since last meeting · what I worked on · what shipped · current status · open follow-ups

Handoff

You decide what to emphasize and how to say it

These tools are good at reconstructing a scattered week. They are not good at deciding what matters politically, or how to talk about it in the room. That part stays yours.