Skip to content
TrustedSkillsbeta
Back to all skills

Gcc

Checked
faugustdev·v1.0.0·backend·MIT

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'.

Repository

Install on your platform

Showing OpenClaw.

  1. 1

    Run this in your terminal

    terminal
    $ openclaw skills install gcc

What we know about this skill

Publisher

faugustdev

Taken from the source listing. We haven't verified who controls this account.

Install target

Pinned to 85c85391

Installs fetch a stored snapshot of that commit, so the code can't change after the fact.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned faugustdev/git-context-controller at 80b7fa5627.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
80b7fa5627
Manifest
SKILL.md
Scanned
11 files, 1,518 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

Git Context Controller (GCC) provides lean, git-backed context management for LLM agents. It stores a combination of hash values, intent descriptions, and optional decision notes instead of lengthy markdown files. GCC offers two modes: one utilizing a Git repository for structured memory and another standalone mode compatible with previous versions.

When to use it

  • Long conversations: When an agent needs to maintain context over extended interactions that would otherwise exceed token limits.
  • Experimentation: To safely test different approaches using Git worktrees, providing isolation for experimentation.
  • Cross-session memory: To reconstruct and leverage past decisions and reasoning across multiple sessions of the AI agent.
  • Vector database integration: When combined with aiyoucli, GCC can automatically feed commit data into a vector memory system.

Key capabilities

  • Lean storage: Stores approximately 50 tokens per entry, significantly reducing context size compared to previous versions.
  • Git-backed truth: Uses Git commits as the source of record for all stored information.
  • Safe experimentation: Enables branching and worktrees for isolated testing.
  • Context reconstruction: Reconstructs full context on demand using git show.
  • Standalone mode: Provides compatibility with previous versions through markdown files.

Example prompts

  • "Show me the last 5 entries in my GCC."
  • "What was the intent behind commit hash abc123?"
  • "Display all decisions recorded in GCC."

Tips & gotchas

  • Requires a basic understanding of Git for optimal use, especially when utilizing the Git-backed mode.
  • The standalone mode offers compatibility but lacks the full benefits of Git versioning and isolation.