sync-gbrain

Synchronize gbrain data with repository state and update CLAUDE.md search guidance.

Updated May 11, 2026
One-click install
npx skills add https://github.com/wodeh/gstack-kimi --skill sync-gbrain-wodeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-gbrain
Source: https://github.com/wodeh/gstack-kimi/tree/main/sync-gbrain
Command: npx skills add https://github.com/wodeh/gstack-kimi --skill sync-gbrain-wodeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps gbrain in sync with the repository state and refreshes agent search guidance in CLAUDE.md, ensuring the brain's indices stay current as code evolves and search quality improves.

Core Features & Use Cases

  • Reconciles gbrain artifacts with the latest repo changes to maintain accurate code understanding.
  • Refreshes agent search guidance in CLAUDE.md to reflect new code, APIs, and surfaces.
  • Runs as a re-runnable, idempotent orchestration with state probing, native code-surface registration, capability checks, and a verdict block.
  • Activated by triggers like "sync gbrain", "refresh gbrain", "reindex repo", and "update gbrain" to keep the knowledge layer aligned with work in progress.

Quick Start

Invoke the skill with a sync gbrain trigger to start the synchronization process.

Frequently Asked Questions about sync-gbrain

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

FAQPage Schema
How do I sync gbrain with current repository changes?

Refresh gbrain indices by triggering the skill to reindex the repository, running state probing and native surface registration to align gbrain artifacts with the latest code changes and improve degraded search results.

What is the best way to update CLAUDE.md agent search guidance?

Update CLAUDE.md agent search guidance by running the gbrain synchronization process, which automatically refreshes search instructions to reflect new code, APIs, and surfaces while maintaining an idempotent state verdict block.

Why are my gbrain search results degrading after code changes?

gbrain search results degrade when repository artifacts fall out of sync with code evolution. Running a gbrain synchronization reconciles the knowledge layer, applies native surface registration, and updates CLAUDE.md to restore search quality.

Can I re-run gbrain synchronization if the repository state changes again?

Yes, gbrain synchronization is re-runnable and idempotent, meaning you can safely execute it multiple times using triggers like "refresh gbrain" without causing duplicate artifacts or conflicting repository states.

Does gbrain synchronization require external dependencies to reindex a repository?

No, gbrain synchronization operates without external dependencies, relying on internal state probing, capability checks, and a verdict block to reconcile repository changes and update agent search guidance independently.