sync-gbrain

Synchronize GBrain indexing and refresh CLAUDE.md search guidance for repositories.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/yashs33244/my-mac-claude --skill sync-gbrain-yashs33244
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-gbrain
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/gstack/sync-gbrain
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill sync-gbrain-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It keeps GBrain up to date for this repo by syncing the brain index and refreshing the agent search guidance in CLAUDE.md, so the assistant can find the right code artifacts and follow the latest navigation conventions.

Core Features & Use Cases

  • Idempotent repo synchronization: Re-runnable sync that probes state, checks capabilities, and produces a deterministic refresh effect without requiring manual cleanup.
  • GBrain indexing refresh: Runs the gstack brain sync flow to ensure semantic code search reflects the current repository contents.
  • Navigation and capability verdicts: Performs state probing, native code-surface registration, capability checks, and returns a verdict block that tells you whether to prefer gbrain search or fallback strategies.
  • Use case: When “gbrain search isn’t finding things” after a refactor, dependency update, or documentation movement, run this skill to re-index and restore reliable search behavior for the repo.

Quick Start

Use the sync-gbrain skill when you want to refresh gbrain indexing and update the repo search guidance after changes, for example by issuing the command: sync gbrain.

Frequently Asked Questions about sync-gbrain

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

FAQPage Schema
How do I refresh semantic code search indexing after a repository refactor?

To fix stale semantic search results after a refactor, run an idempotent synchronization workflow that re-indexes the repository and updates agent navigation guidance. This routine safely refreshes the search state without requiring manual cleanup before execution.

What is the best way to update repo-specific search guidance for an AI coding assistant?

The best way to update repo-specific search guidance is to synchronize the brain index and refresh the agent search instructions in your configuration file. This process allows the assistant to find correct code artifacts and follow the latest navigation conventions.

Does the gstack brain sync workflow support safe repeated executions on macOS?

Yes, the gstack brain sync workflow supports safe repeated executions on macOS by using an idempotent update flow. Running the synchronization routine repeatedly produces a deterministic refresh effect without requiring manual cleanup between runs.

Why does semantic code search stop finding things after a dependency update?

Semantic code search stops finding things after a dependency update because the brain index becomes stale relative to the new repository state. Running a synchronization routine re-indexes the contents and restores reliable search behavior.

Can I run a targeted re-indexing routine for specific codebase changes?

Yes, you can run a targeted re-indexing routine because the synchronization workflow supports targeted scenarios alongside full updates. It probes the current state and performs capability checks to apply updates exactly where codebase changes occurred.