sync-gbrain

Synchronizes the gbrain search index with the current repository state for accurate semantic code retrieval.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, jq, gbrain, and includes scripts (resource) components.

What problem does it solve?

This skill ensures that your gbrain search index remains synchronized with the latest code changes in your repository, preventing stale search results and ensuring the agent has accurate context for symbol-aware lookups.

Core Features & Use Cases

  • Repository Indexing: Triggers a refresh of the gbrain search guidance and index to reflect current code state.
  • State Management: Orchestrates the gstack-gbrain-sync process while maintaining session state and telemetry.
  • Use Case: After performing a large refactor or adding new features, use this skill to ensure that subsequent semantic queries via gbrain accurately reflect the new codebase structure.

Quick Start

Invoke the sync-gbrain skill to refresh the repository index and update search guidance.

Frequently Asked Questions about sync-gbrain

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

FAQPage Schema
How do I synchronize my code search index with recent repository changes?

Synchronizing your code search index requires refreshing the gbrain search guidance to reflect current code state, ensuring semantic code retrieval accurately matches your latest repository updates and structural changes.

Why does semantic code search return stale results after a refactor?

Semantic code search returns stale results when the search index is not synchronized with current repository state, requiring an index refresh to update context and ensure accurate symbol-aware lookups.

What's the best way to update search guidance after adding new features?

Updating search guidance after adding new features involves triggering a gbrain index refresh, which orchestrates idempotent updates to align the semantic search context with the new codebase structure.

Do I need gbrain binaries and local repository configuration to perform indexing?

Performing indexing requires access to gbrain binaries and local repository configuration, operating within the gstack environment to manage session state, telemetry, and configuration-driven updates.

Can I use gstack to manage session state during search index synchronization?

You can use gstack to manage session state and telemetry during search index synchronization, orchestrating the gstack-gbrain-sync process while maintaining configuration-driven indexing for idempotent updates.

When should I not use an automated repository indexing approach?

Automated repository indexing is not suitable when gbrain binaries are inaccessible or local repository configuration is missing, as the synchronization process depends on these components to execute idempotent updates.