Ctx Branch

Effect

Bind a Git branch name to a sub-context. When you switch branches, the corresponding sub-ctx switches too. Each branch independently tracks “what’s been done and what remains.”

When to Use

• 3+ feature branches running in parallel
• Each branch has a distinct scope (deploy prep, feature dev, refactor, etc.)
• You catch yourself asking “what was I doing on this branch?”

How It Works

1. Add branch info to the parent ctx’s Sub Contexts table

## Sub Contexts

| Theme | File | Branch |
|-------|------|--------|
| ReAct Agent | project/react-agent.md | feature/react-agent |
| GCP Minimal Deploy | project/gcp-minimal.md | deploy/gcp-minimal |
| UI Refresh | project/new-ui.md | feature/new-ui |

2. Include branch info in the sub-ctx

# GCP Minimal Deploy — Sub ctx

**Parent ctx**: project_resume.md
**Branch**: deploy/gcp-minimal
**Last updated**: 2026-03-30

## Scope
What this branch covers.

## Steps
Branch-specific task list.

## Notes
Branch-specific decisions and constraints.

3. Workflow

On branch switch:
  git checkout feature/X
  → Read sub-ctx project/X.md
  → Branch context is instantly restored

On task completion:
  Update sub-ctx (check off TODOs)
  → Add 1 line to parent ctx Timeline
  → Commit

On branch merge:
  Mark sub-ctx as "done"
  → Record integration result in parent ctx

Combinations

Card	Synergy
Ctx Tree	Prerequisite. Branch links sub-contexts from the Tree
Dryrun	Record pre-validation before cutting a branch
Ship	Branch shipping decision → sub-ctx done → merge

---

“A branch is a plan; context is memory. Only with both can you manage parallel worlds.” — Eris

Want to use this card permanently? Convert it directly into a SKILL.md — Effect → Overview, When to Use → Trigger, How It Works → Steps.