git-context-controller

Topics in the source

• Git Context Controller (GCC)
• Overview
• Initialization
• Configuration
• Commands
• COMMIT
• BRANCH
• MERGE

GCC transforms agent memory from a passive token stream into a structured, versioned file system under .GCC/. Inspired by Git, it provides four operations — COMMIT, BRANCH, MERGE, CONTEXT — to persist milestones, explore alternatives in isolation, synthesize results, and recover historical context efficiently. On first use, check if .GCC/ exists in the project root. If not, run scripts/gccinit.sh to create the directory structure: For detailed file format specifications, read references/fileformats.md. GCC behavior is controlled via metadata.yaml: proactivecommits: true — Automatically suggest commits after completing coherent sub-tasks proactivecommits: false — Only commit when explicitly requested Toggle with: "enable/disable proactive commits" or by editing metadata.yaml. Persist a milestone on the current branch. Triggers: /gcc commit , "commit this progress", "save this milestone", "checkpoint" Procedure: 1. Read the current branch's commit.md to determine the next commit number 2. Append a new entry to commit.md with: Sequential ID (e.g., [C004]) Date (UTC ISO 8601) Current branch name Branch purpose (from summary.md if on a branch, or from main.md) Previous progress summary

This is an excerpt. Refer to the complete source and its current requirements.