项目文件夹

文件
Asim Aslam 5f3244d09e feat(cli): add micro loop to scaffold a self-improving repo loop (#3649)
`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>
2026-07-02 10:12:12 +01:00

871 B

North Star

Edit this file. It is the single source of direction the loop aligns every increment to. The planner ranks work against it; the builder builds toward it. Be concrete — vague direction produces vague increments.

Mission

<One or two sentences: the problem this repository solves and who it's for.>

Right now

<The current priority — what "better" means this month. The planner weights the queue toward this.>

Guardrails

  • One concern per PR; small and reversible.
  • The gate is green CI, not a human review — keep the test/lint suite strong, because the loop is only as good as its evaluator.
  • Off-limits without a human (surface as notes, never auto-merge): breaking public API changes, brand/positioning/marketing copy, new dependencies, architectural rewrites, product-default changes with broad behavioral impact.