skills.rest
Walrus-Computing
Walrus-ComputingOFFICIAL
Explore all skills by this author →
GitHub

sync-gbrain

Refresh gbrain search guidance and repository indexing for the current codebase.

20|3|Updated Apr 2, 2026
Search Tags:#indexing#semantic search#idempotent#repository sync#claude md#gbrain
One-click install
npx skills add https://github.com/Walrus-Computing/piper-draw --skill sync-gbrain-walrus-computing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-gbrain
Source: https://github.com/Walrus-Computing/piper-draw/tree/main/.claude/skills/gstack/sync-gbrain
Command: npx skills add https://github.com/Walrus-Computing/piper-draw --skill sync-gbrain-walrus-computing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps gbrain search aligned with the repository so agents can find current code, follow the right routing guidance, and avoid stale search results.

Core Features & Use Cases

  • Repository re-sync: Rebuilds the gbrain view of this repo after code changes so semantic search stays current.
  • Agent guidance refresh: Updates CLAUDE.md search and routing hints so future sessions know when to use gbrain tools.
  • Safe reruns: Designed to be idempotent, with state probing, capability checks, and a clear verdict block for repeated use.
  • Use case: Run it after major refactors, indexing failures, or when the agent cannot find symbols, files, or recent changes.

Quick Start

Use this skill to refresh gbrain for the repository and update the agent guidance in CLAUDE.md.

Frequently Asked Questions about sync-gbrain

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

FAQPage Schema
Why does semantic search fail to find recent code changes in my repository?▼

Semantic search fails when the repository index is stale. Re-running a repository sync rebuilds the search view against your current codebase so agents can reliably find updated files and symbols.

How do I update CLAUDE.md routing guidance for semantic search?▼

Updating CLAUDE.md routing requires refreshing agent guidance hints. This sync process rewrites search and routing instructions in CLAUDE.md so future sessions know when to use gbrain tools.

When should I rebuild repository indexing after a major refactor?▼

Rebuild repository indexing immediately after major refactors, indexing failures, or when agents cannot locate symbols. Re-syncing ensures semantic search stays current and avoids stale results.

Can I safely rerun repository sync operations multiple times?▼

Yes, you can safely rerun repository sync operations. The task is designed for idempotent execution with state probing and capability checks, ensuring repeated runs produce a clear verdict block without duplication.

What is the best way to troubleshoot semantic search not surfacing relevant files?▼

Troubleshooting semantic search involves probing state and checking capabilities before reindexing. A full repository sync refreshes the search guidance and native code-surface registration to resolve missing files.

Related Skills

Explore More Software Engineering Skills→
anilveersingh1308anilveersingh1308

gstack-sync-gbrain

Run the gstack-gbrain-sync orchestrator to refresh gbrain indexing and search alignment.

Community
Advanced
smarmen86smarmen86

sync-gbrain

Synchronize the gbrain search index with repository state and refresh CLAUDE.md routing rules.

Community
Advanced
mirakuimirakui

databricks-vector-search

Create Databricks Vector Search endpoints and Delta Sync indexes for RAG retrieval.

Community
Advanced
MacPhobosMacPhobos

Vector Search Workflows (MCP Vector Search)

Index codebases into ChromaDB and perform semantic searches via mcp-vector-search.

Community
Intermediate