OpenClaw Starter Packs

Engineers with too many repos and no time for maintenance

Opportunist

Opens small improvement PRs across your repos every night. Closes them if you don't merge by the next day. Gets better at guessing what you'll want.

Buy for $199 Back to packs

Outcomes

  • • Deps, docs, and tests inch forward every day without you scheduling time for them
  • • Ignored PRs close themselves — your repos stay clean
  • • After a few weeks it knows what you merge and stops suggesting what you skip

What is included

How the agent works

  • • Nightly opportunistic improvement generator
  • • Low-noise PR batching, 1–3 PRs max by default
  • • Auto-close stale PRs the next evening to keep repos clean

Files you'll fill out

  • • Repo registry and allowed scopes
  • • PR preference model, what you like and what to skip
  • • Merge and rejection signals to fuel the learning loop

Step-by-step workflows

  • • Nightly scan → plan → PR creation workflow
  • • Next-day cleanup: close what was ignored, log why
  • • Learning loop: classify merged PRs and update preferences so the next batch is better

Conversation preview

Preview: Opportunist in action

Me

I have 12 repos and I never do maintenance. Can you just make progress for me every day?

Opportunist

Yes—low-noise and safe. First: which repos are in scope, what changes are allowed (docs/deps/tests/etc), and your noise budget (e.g., max 2 PRs/night)? Then I’ll generate nightly PR proposals; if you enable it, I can open them on branches and auto-close anything you don’t merge by the next day.

Illustrative conversation preview. PR opening/closing can be approval-gated; merges are always manual.

Memory files

  • • repo_registry.md
  • • pr_preferences.md
  • • nightly_queue.md
  • • merge_signals.md
  • • safety_rules.md
  • • decisions.md

Context questions at startup

  • • Which repos are in scope, and which are explicitly off-limits?
  • • What PR types do you want (docs, deps, refactors, tests, lint, perf)? What is forbidden?
  • • What is your noise budget (max PRs per night) and auto-close window?
  • • What are the safety gates (CI must pass, no prod changes, no lockfile churn, etc.)?

Tools guidance

  • • git and branching workflow
  • • GitHub PR creation and closing, approval-gated settings
  • • CI awareness, never bypass failing checks
  • • scoped repo access and rate limits

Opens small nightly PRs, closes what you ignore the next day, and learns which types you'll actually merge.