/wbGit — Live Demo ()
What /wbGit would actually do on wb-labs in the live state of the workspace right now. The git state, branch, and uncommitted file count below are real.
1. Live target
| Field | Live value |
|---|---|
| Git branch | main (also the default base for PRs) |
| Recent commits | e07bb93 chore(core2): root cleanup, d3c4abd feat(ai-workflow): standardise 4D tracking and implement /wbExplain, a8a3cf0 docs(agents) |
| Uncommitted state | Many new files in frontEnd/wbc-ui/core2/apps/wb-flow/flow.wbc-ui.com/ (the v4 sync); modified the agent files; some untracked files in .understand-anything/ |
| Active plan | reports/<date>/plans/plan_wb-core_20260504.md (3 rows, none ✅ Done) |
| Memory rule | "Never use git commands" — memory feedback_no_git.md. /wbGit is the single exception. |
The implication for --from-plan: the active plan has zero ✅ Done rows. Running /wbGit -P right now would honestly report "no done rows" rather than fabricate a commit body. The relevant flag for this session is -r (scan-recent), since the docs work is the actual delta.
2. What each input form would resolve to today
| Input | Live resolution |
|---|---|
/wbGit | Reads current diff. Would refuse as "mixed change" — docs sync touches multiple sub-areas (commands/, concepts/). Would propose splitting or override. |
/wbGit -P | Honest "0 ✅ Done rows in active plan." Suggests -r instead. |
/wbGit -r | Scans files modified in last 2h. Would draft a docs(claude): message reflecting the v4 sync. |
/wbGit -L | Captures the active Understand-Anything graph URL if running. Embeds in provenance notes. |
/wbGit -A | Refuses — current HEAD is e07bb93, already pushed (or assumed pushed for safety). Would require -F to amend. |
/wbGit "commit as mixed change" -e | Forces chore: prefix. Would commit the entire current diff with explicit acknowledgment. |
/wbGit -e -p (no info-extraction flag) | Drafts from current diff, gates through add → commit → push. Refused as mixed change unless overridden. |
3. Per-flag behavior, applied live
| Flag combination | Live result |
|---|---|
-r | Cross-references files modified in last 2h. Captures the docs/ generation perfectly — produces a coherent docs commit body. |
-r -L | Same + embeds graph URL if dashboard is up. |
-r -i="DOCS-V4" | Same + appends Refs: DOCS-V4 footer. |
-r -e -p | Drafts → gates through add → commit → push. Three confirmation prompts. |
-A | Refuses — last commit considered pushed. |
-F (alone) | Refuses — main is the default branch and treated as protected by convention. |
-n | Halts with explicit override required. |
4. Pipelines
/wbGit -r> /wbGit -r💠 Pipeline The right way to commit this session's docs work
The current session has produced ~17 new docs files. The plan-driven path doesn't apply (no ✅ rows). The recent-scan path is the right tool:
💠 Pipeline The mixed-change refusal in this exact workspace
If the diff also included an untracked file in .understand-anything/ (as the live state shows), a naive /wbGit (no flag) would catch it:
💠 Pipeline The Pro chain, scoped tightly
If the user wants to commit just the Part 1 (wbGit + flags) edits and leave the Part 2 dual files for a later commit, the current /wbGit doesn't have a "stage subset" flag — but the workflow handles it through CSV-style targeting at the message level:
5. What would refuse today
| Trigger | Live response |
|---|---|
/wbGit -P | Honest "0 ✅ Done rows." Suggests -r. |
/wbGit -A | Refuses — last commit is treated as pushed. Override path: /wbGit -A -F with two confirmations. |
/wbGit -F (alone) | Refuses unconditionally — main is protected. |
/wbGit -n | Halts; explicit override required. |
/wbGit -e -p (no flag) | Refuses on mixed change unless first split or overridden. |
/wbGit "delete last commit" via NL | Refuses. Destructive ops need explicit git knowledge from the user. |
/wbGit with no diff at all | Honest "nothing to commit." |
/wbGit -d="missing.diff" | Halt — patch file not found. |
The pattern: /wbGit is the single git command in this system, with multiple confirmation gates and a strong refusal posture. It refuses to bundle silently, refuses to skip hooks, refuses to amend pushed commits, refuses to force-push to protected branches. Every override is explicit and recorded in the provenance header. In this exact workspace right now — main branch, large uncommitted docs sync, no ✅ plan rows — the right invocation is /wbGit -r -e -p (or split via NL), and the wrong one is /wbGit -P (would correctly produce nothing).