repo-topology
Choose monorepo versus separate repositories and record the resulting topology decision.
- License 许可
- MIT
- 最近更新
- 2026-08-08
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- repo-topology
- description
- Choose monorepo versus separate repositories and record the resulting topology decision.
03 SKILL.md 正文
Consult: Repository Topology
Outcome
Decide monorepo versus separate repositories and record the decision. When splitting, produce per-component repositories and a thin top-level coordination repo, without losing template state.
Method
- Ask monorepo vs separate repos. Recommend monorepo for small teams and single-runtime projects.
- Separate repos: each component directory gets its own
git init, its ownflake.nixdevshell, Dockerfile, CI workflow, and a sliced README/AGENTS. The top-level checkout becomes a thin coordination repo that tracks the component repos as git submodules and keepsHANDOFF.toon, cross-repo compose topology, and cross-cutting docs. - Register submodules with relative paths immediately; fix up remote URLs when the sub-repos are pushed. If remotes are unknown, record a revisit trigger in the profile rather than blocking.
Guards
- A dirty working tree blocks the split: ask the user to commit or stash first.
- Never remove a dirty worktree.
Outcome recording
- Write the monorepo-vs-separate-repos decision to
PROJECT_PROFILE.toonas a decision entry, ending in a documented decision. Never leave it resolved only in conversation. - This is the most irreversible decision in the consult cluster: splitting
runs
git initper component and converts the top-level checkout into a submodule tracker. Record it as an ADR underdocs/decisions/, not only a profile entry. - When splitting, also record per-component repo state (registered
submodules, pending remote URLs, any revisit trigger) in
PROJECT_PROFILE.toon.
Do not
- Split without an explicit decision.
- Discard
.agents/,.agentic-template/,PROJECT_PROFILE.toonorHANDOFF.toonwhen carving components.
04 同仓库更多 Skills
agentic-template
Start or continue work in this repository using the canonical AGENTS.md contract and repository skill catalog.
wiki-tidy
Reconcile the wiki against the knowledge graph, specs and code; prune stale, keep links resolving.
update-handoff
Update HANDOFF.toon with current semantic work state.
test-first
Drive meaningful behaviour changes with the smallest useful failing test.
test-change
Select and run tests that prove a change at suitable fidelity.
specify
Create proportional OpenSpec-shaped structured change proposals for meaningful changes.