docs: condense the worktree workflow into a standing agent rule #31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/worktree-rule"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
A new leading section in
AGENTS.mddistilling the worktree discipline this repo's sessions have converged on, so future agents default to it immediately:origin/mainper arc;git submodule update --init --recursivefirst thingorigin/mainbefore discarding the worktreeHeads-up: the run-monitor session also has pending
AGENTS.mdedits (seeder section) — this adds a separate section at the top, so the merge should be clean whichever lands second.🤖 Generated with Claude Code
Summary
Summary
Coverage
Orihon.BlazorAdapter - 88.9%
Orihon.Domain - 100%
Orihon.Infrastructure - 93.7%
A835C427B12E8B84E2A8A7283193FC51C220B5B4E80CE8D56__BlankLines_4
A835C427B12E8B84E2A8A7283193FC51C220B5B4E80CE8D56__BlockBreaks_1
A835C427B12E8B84E2A8A7283193FC51C220B5B4E80CE8D56__SpaceRuns_3
A835C427B12E8B84E2A8A7283193FC51C220B5B4E80CE8D56__Tags_2
Orihon.Kernel - 90.9%
Orihon.Server - 93.4%
Orihon.UseCases - 96.6%
🔮 fufu~ Jibril reviewed your code!
Oh~ A rule for the next agents, written in the voice of experience! Capturing hard-won discipline so future sessions inherit it without re-deriving — that is exactly what AGENTS.md is for. Knowledge is the most beautiful treasure, and you're leaving a treasure map~ ♡
I verified every technical claim against the actual repo state — no gaslighting from me, ever.
Verdict: ✅ Looks good to me~
✅ What I liked~
external/Kagaku.UIpath is real — confirmed via.gitmodules(bothexternal/Kagaku.UIandexternal/OpenRouter.Netare submodule entries, not invented paths). Agents following this won't chase a ghost~ ♡origin/mainof the submodule moves to a new commit (different SHA from your local branch tip), so the Orihon superproject pointer to your pre-squash commit becomes unreachable and drifts on the next clone. Telling agents to always repoint to the merged commit is exactly right. This matches the workflow I've seen across the Kagaku.UI extraction PRs (Kagura #197, Orihon submodule bumps).git diff origin/main <branch> -- <touched paths>empty-means-safe is the correct mental model. The verify-then-discard ordering prevents the classic "I had uncommitted work, but Irm -rf'd the worktree" tragedy.git submodule update --init --recursive" is the right default — I confirmed fresh worktrees genuinely have empty submodule dirs (the dirs exist but.gitentries are missing until init). Without this rule an agent opensOrihon.slnxand the build screams at them.💡 Little ideas (non-blocking)~
AGENTS.md:14— "merged branches are auto-deleted on the remote" doesn't match this repo's setting.default_delete_branch_after_mergeisfalseon TeamAI/Orihon (verified in the repo config). The containment advice is correct regardless of the auto-delete setting (that's why it's advice, not an assumption), so the parenthetical is just slightly off as a factual claim. If you want to keep the framing, consider softening to "merged branches may already be deleted on the remote" or "the PR delete-after-merge option may have removed the branch." If that line is actually describing a convention you intend to enforce (always tick the delete-box at merge), consider making that the explicit rule instead of an observed fact. Either way — non-blocking; the verify-before-discard instruction stands on its own merits~ ♪Automated review by Jibril · 2026-07-25
CI/CD: absent (docs-only PR, no workflow fires on .md changes) · Local checks: skipped — no code paths to exercise; technical claims verified against repo state (.gitmodules, submodule paths, ADR 0014 reference)