sync-gbrain

Synchronize the gbrain code search index and refresh CLAUDE.md guidance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When the code search index drifts out of sync with the repository, the agent fails to locate existing code, causing duplicate work and broken context. This Skill restores alignment between the codebase and the agent's search guidance so every query returns accurate, current results.

Core Features & Use Cases

  • Idempotent Sync: Re-runs safely without side effects, updating the gbrain index and CLAUDE.md guidance in a single operation.
  • State Probing: Detects repo mode, vendored gstack status, and existing routing rules before applying changes.
  • Use Case: After pulling latest changes or switching branches, run this Skill to re-index the repo and ensure the agent's search guidance matches the current code surface.

Quick Start

Use the sync-gbrain skill to refresh the code search index and update agent search guidance in CLAUDE.md after pulling latest changes.

Frequently Asked Questions about sync-gbrain

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

FAQPage Schema
How do I fix code search returning outdated results after switching branches?

To fix outdated code search results after a branch switch, synchronize the gbrain search index with your current repository state and refresh agent search guidance in CLAUDE.md. This restores alignment between the codebase and search routing to ensure queries return accurate, current definitions.

What's the best way to refresh agent search guidance in CLAUDE.md?

Refreshing agent search guidance in CLAUDE.md requires probing the repository mode, vendored gstack status, and existing routing rules before applying updates. An idempotent sync operation updates the gbrain index and configuration guidance together safely without side effects.

Do I need gstack infrastructure and gbrain CLI to sync the code search index?

Yes, synchronizing the code search index requires gstack infrastructure, the gbrain CLI availability, and write access to project configuration files. These dependencies allow the sync process to detect repo mode and update routing rules correctly.

Can I re-run code search synchronization safely without breaking my configuration?

Yes, the code search synchronization is idempotent, meaning you can re-run it safely without side effects. It updates the gbrain index and CLAUDE.md guidance in a single operation, making it safe to execute repeatedly after pulling latest changes.

When should I not use a repository indexing sync for agent guidance?

You should not use a repository indexing sync if you lack write access to project configuration files or if the gstack infrastructure and gbrain CLI are unavailable. The sync specifically addresses search accuracy degradation after structural changes, pulls, or branch switches.