Git Context Controller (GCC)

Trust Score 86/100

Lean, git-backed agent memory tool that stores commit hashes + intent and provides COMMIT/BRANCH/MERGE/CONTEXT commands to reconstruct context on demand.

triggers:/gcc commit/gcc branchcommit this progresswhere were wecontext --summarygit-backed memoryai memory bridge

GitHub SKILL.md

What it does

GCC provides a lightweight memory layer for agents by recording concise timeline entries (hash + intent + optional notes) backed by git. It reconstructs full context on demand via git, enabling cheap summaries and deep dives while avoiding verbatim storage of large markdown memories.

When to use it

Persisting milestones or decisions as compact entries.
Creating isolated experiment worktrees (branching) for agents.
Recovering context across sessions with summary or deep-dive commands.

What's included

Scripts: init, commit, context, bridge, cleanup scripts (described in the SKILL.md) to manage index.yaml, worktrees, and optional bridge to vector memory.
References: none indicated in the repo for this skill.
Instructions: procedures for COMMIT/BRANCH/MERGE/CONTEXT/CLEANUP and natural-language trigger mappings.

Compatible agents

Works with agent frameworks that can run repo scripts and manage git (Copilot/Codex-like agents, CLI-capable LLMs, or custom agent runners).

Audit Summary

GCC is a git-backed agent memory tool providing COMMIT/BRANCH/MERGE/CONTEXT commands via lean index.yaml. Init script works cleanly in standalone mode; other scripts correctly require initialization first. Well-structured shell scripts with proper error handling and dual-mode support (git/standalone). No security concerns — all operations are local, no remote calls except optional aiyoucli bridge.

Watch Out

Scripts must be run after gcc_init.sh — they exit with clear errors otherwise
YAML parsing via awk is fragile for complex/nested values but works for the expected schema
aiyoucli bridge is a no-op if that tool isn't installed (graceful degradation)

Notes

Solid skill with clean architecture. Dual git/standalone mode is well-designed. The aiyoucli bridge is optional and silent when unavailable. Scripts are idempotent and handle edge cases. Minor deduction for YAML parsing fragility and some awk pattern repetition across scripts.

Information

Repository: git-context-controller
Stars: 44
Installs: 0

Trust Score

Overall86

Security92

Code Quality78

Architecture82

Usefulness65

Related Skills

Reverse Engineer

Provides step-by-step guidance and best practices for binary reverse engineering: static analysis, dynamic tracing, disassembly, and documentation workflows for

Caveman Compress

Compress natural-language memory files into a compact 'caveman' format to save LLM tokens while preserving code, links, and structure.

JJ Hunk

Programmatic hunk selection for Jujutsu (jj): list, split, commit, or squash specific hunks to enable partial commits and fine-grained history editing without a

Overnight — Autonomous Long-Running Coding

Orchestrates long-running coding goals: decomposes objectives into atomic tasks, dispatches isolated worktree workers, verifies acceptance criteria, and merges

Go Data Structures

Authoritative guidance on choosing and using Go built-in and standard-library data structures, with practical best practices for slices, maps, arrays, container

Memory Search

Search past coding sessions and observations using natural-language queries to retrieve decisions, notes, and context.

Claw Release

Release automation for OpenClaw skills: version bumping, tagging, packaging, and CI verification for skill releases.

Matrix Warnings

Manage file and package warnings (add, remove, list, check) for a Matrix workflow; parse user arguments and call the matrix_warn tool to enforce repository-leve

Back to Skills