docs(skills): a Mind ledger push lands itself — stop leaving branches hanging - #306
Merged
Merged
Conversation
… hanging PyAutoMind now auto-merges a ledger-only `claude/**` push into main and deletes the branch (mind_ledger_merge.yml). Every skill that mutates Mind state ends in `prompt_sync_push`, so the fact belongs once in WORKFLOW.md — the shared page they all point at — rather than in ten skill bodies. /prm step 5.4 said "push Mind on `main`", which is wrong on every branch-scoped surface and is exactly where the close-out's ledger commit was stranding. It now says push the branch you are on, names the three outcomes (lands by itself / waits for a human because the diff touched code / never was going to merge because `lifecycle.py check` fails), and gives the one command that tells them apart before the push. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CmGdNA97ajAyLJ4jemvki8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
PyAutoMind now auto-merges a ledger-only
claude/**push intomainand deletes the branch — PyAutoMind#358,mind_ledger_merge.yml. The skills need to know, or they will keep reporting Mind state as "pushed, awaiting merge" when it has already landed, and keep asking humans to merge branches that merge themselves.What changes
skills/WORKFLOW.md— every skill that mutates Mind state ends inprompt_sync_push, so the fact belongs once on the shared page they all point at, not in ten skill bodies. It now says:prompt_sync_pushpushes the branch you are on, that is the whole job either way, and a ledger-only push lands unattended. It also names the code side of the gate, so a skill whose diff also touchedscripts/or.github/says "waits for a human" rather than implying the state landed.skills/prm/prm.md— step 5.4 said "push Mind onmain". That is wrong on every branch-scoped surface (the phone, claude.ai/code, anyclaude/**flow) and is exactly where the close-out's own ledger commit was stranding:/prmwould move the prompt tocomplete/, regenerate the dashboard, commit it — and leave it on a branch nobody merged.It now says push the branch you are on, never force
main, and names the three outcomes explicitly:lifecycle.py checkfails → it was never going to merge; fix the drift.Plus the one command that tells them apart before the push (
ledger_merge.py classify --base origin/main), and a note under Notes that Mind's own close-out commit is the one case needing no PR at all.Validation
569 tests (
-n auto),ruffclean. Documentation-only — no entrypoint, registry or agent behaviour changes.Generated by Claude Code