sync-gbrain

Sync the gbrain index and refresh agent search guidance in CLAUDE.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps gbrain indexing current with the repository and refreshes agent search guidance in CLAUDE.md.

Core Features & Use Cases

  • Re-syncs the gbrain index with the repository state and surfaces updated guidance for code search.
  • Probes repository health, registers native code surfaces, runs capability checks, and emits a verdict block to CLAUDE.md.
  • Use Case: When gbrain search yields stale results, run sync-gbrain to refresh indexing and update guidance.

Quick Start

Run /sync-gbrain to refresh the gbrain index and update CLAUDE.md guidance.

Frequently Asked Questions about sync-gbrain

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

FAQPage Schema
How do I refresh stale semantic code search results in my repository?

You can refresh stale semantic code search results by running a repository index sync that updates CLAUDE.md guidance. This re-indexes the codebase and registers native code surfaces to resolve outdated search outcomes.

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

Updating CLAUDE.md guidance involves syncing the repository index to probe repository health and register native code surfaces. This emits a verdict block that refreshes agent search guidance safely and idempotently.

Why does my gbrain search yield outdated results after repository changes?

gbrain search yields outdated results when the repository index falls behind the current codebase state. Running an index sync operation refreshes the semantic search data and updates CLAUDE.md guidance to match.

Can I run repository indexing multiple times without causing side effects?

You can run repository indexing multiple times safely because the sync operation is re-runnable and idempotent. It safely refreshes search index data and CLAUDE.md guidance without causing duplicate or conflicting side effects.

Does repository indexing require any external dependencies to update search guidance?

Updating search guidance requires no external dependencies. The sync operation natively probes repository health, runs capability checks, and registers code surfaces to emit guidance directly into CLAUDE.md without external packages.