micro--go-micro
Asim Aslam
5f3244d09e
`micro loop init` writes an autonomous improvement loop into any repository —
the same planner/builder/triage loop that maintains go-micro, generalized:
- planner (loop-planner.yml): keeps a ranked queue in .github/loop/PRIORITIES.md
- builder (loop-builder.yml): builds the top open item as a single-concern PR,
auto-merged on green CI
- triage (loop-triage.yml): turns CI failures into scoped fix issues
plus .github/loop/NORTH_STAR.md (direction) and PRIORITIES.md (queue).
The agent adapter is mention-based, not hardcoded to Codex: `--agent @codex`
(or any @mention agent that responds on an issue and can run gh), `--token-secret`,
`--branch`, `--ci-workflow`, and cron flags are the whole config-vs-core boundary.
Templates use << >> delimiters so GitHub Actions' own ${{ }} expressions pass
through untouched. `micro loop verify` checks the wiring and flags the two things
the CLI can't: the token secret and branch protection (the green-CI gate).
Built inside go-micro with the config/core split already drawn, so the workflows
can later be extracted to a standalone reusable-workflows repo without a rewrite.
Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL
Co-authored-by: Claude <noreply@anthropic.com>
17 行
594 B
Markdown
17 行
594 B
Markdown
# Priorities
|
|
|
|
A single ranked queue, highest-value first. Each item links a scoped issue the
|
|
loop can build and CI can verify. The **planner** keeps this current; the
|
|
**builder** takes the top item whose issue is still open.
|
|
|
|
<!--
|
|
Seed this with a few real items to give the loop a running start, e.g.:
|
|
|
|
1. Add retry with backoff to the HTTP client — #123
|
|
2. Document the config file format — #124
|
|
3. Fix flaky timeout in the cache tests — #125
|
|
|
|
The planner will re-rank, drop completed items, and file issues for new gaps.
|
|
Reorder or edit this file at any time to redirect the loop.
|
|
-->
|