gcc

Store git-backed context entries with hashes and intents in index.yaml.

60|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/faugustdev/git-context-controller --skill gcc-faugustdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gcc
Source: https://github.com/faugustdev/git-context-controller/tree/main
Command: npx skills add https://github.com/faugustdev/git-context-controller --skill gcc-faugustdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aiyoucli, aiyoucli-mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

GCC replaces verbose, hard-to-trace context with a lean, git-backed memory index, enabling context reconstruction on demand.

Core Features & Use Cases

  • Git-mode: real, lean commits in index.yaml with hash, intent, and optional notes
  • Standalone mode: Markdown fallback for non-git projects
  • aiyoucli bridge: optional memory bridging to a vector store for cross-session recall
  • Cross-session recovery: reconstruct context from hashes and decisions

Quick Start

Install GCC and run scripts/gcc_init.sh to begin recording lean context data.

Frequently Asked Questions about gcc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage long-term context for AI agents without bloating the prompt?

To track AI agent decisions, use a versioned index.yaml to record lean commits containing the git hash, intent, and optional notes. This mechanism replaces verbose markdown with a traceable memory index.

Can I record AI agent memory in non-git projects?

To start recording lean context data, install the required dependencies and run the initialization shell script. This sets up the versioned index.yaml and configures the environment for git-backed memory tracking.

What is the best way to recover cross-session context for AI agents?

For cross-session recall, you can use an optional memory bridge to a vector store. This bridges lean git entries to a vector memory system, enabling deeper recall across multiple sessions.

Does git-backed context management support vector memory integration?

You should not use verbose markdown for context management when you need traceability. Use a lean index referencing git hashes instead, because verbose markdown is hard to trace and bloats long-term context.