Agent skill · operations · davila7
gcc
Git Context Controller (GCC) - Manages agent memory as a versioned file system under .GCC/. This skill should be used when working on multi-step projects that benefit from structured memory persistence, milestone tracking, branching for alternative approaches, and cross-session context recovery. Triggers on /gcc commands or natural language like 'commit this progress', 'branch to try an alternative', 'merge results', 'recover context'.
Why this skill is useful
Adds a comprehensive set of executable scripts for managing agent memory with version control, enabling structured project tracking and context recovery.
What it needs
Requires bash installed locally. About 4k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
Git Context Controller (GCC) Overview 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. Initialization 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. Configuration 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. Commands COMMIT Persist a milestone on the current branch. Triggers: /gcc commit <summary>, "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 (1-2 sentences from last commit) This commit's contribution (detailed technical description with files touched) 3. Append an OTA entry to log.md recording the commit action 4. Update metadata.yaml file tree if files were created/modified 5. If on main branch, update milestones section in main.md Proactive behavior: When proactivecommits: true, suggest a commit after: Completing a function, module, or coherent unit of work Fixing a bug and verifying the fix Finishing a research/exploration phase with conclusions Any point where losing context would mean re-doing significant work BRANCH Create an isolated workspace for exploring an alternative approach. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/git-context-controller