sync-gbrain

Refresh the gbrain index and AGENTS.md routing guidance after repository changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When your gbrain index falls out of sync with your repository's code, agent search returns outdated or missing results, and AGENTS.md guidance becomes stale, leading to incorrect context and routing for development tasks.

Core Features & Use Cases

  • Idempotent gbrain sync: Re-run this skill anytime after code changes to refresh the gbrain index without creating duplicate or corrupted state.
  • Agent search guidance refresh: Automatically updates routing rules and context guidance in your project's AGENTS.md file to match current codebase structure.
  • State and capability checks: Verifies gbrain configuration, repo mode, and existing routing rules before performing sync operations to avoid unnecessary work.
  • Use Case: After pushing a large refactor that adds new modules and updates existing APIs, run this skill to ensure gbrain search and agent routing immediately reflect the new codebase state.

Quick Start

Use the sync-gbrain skill to refresh your gbrain index and agent search guidance after making changes to your repository.

Frequently Asked Questions about sync-gbrain

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

FAQPage Schema
How do I refresh my semantic code search index after making repository changes?

Yes, updating agent routing rules in AGENTS.md automatically keeps your development workflow context current. A sync process verifies existing routing rules and updates guidance to match the current codebase structure.

Why does my agent search return outdated or missing results after a code refactor?

Agent search returns outdated or missing results after a code refactor because the gbrain index falls out of sync with repository code changes. Running an idempotent sync refreshes the index and restores accurate context routing.

Can I re-run a codebase indexing sync multiple times without corrupting the state?

Yes, you can re-run a codebase indexing sync multiple times safely. The process is idempotent, meaning it updates the gbrain state and AGENTS.md guidance without manual intervention or creating duplicate entries.

What is the best way to keep agent search guidance current with my codebase structure?

The best way to keep agent search guidance current is to run an idempotent sync that automatically updates AGENTS.md routing rules. This verifies gbrain configuration and existing rules before applying state and capability checks.

Does the gbrain sync process check repo mode and configuration before updating?

Yes, the gbrain sync process performs state and capability checks to verify gbrain configuration, repo mode, and existing routing rules. This avoids unnecessary work before performing the actual sync operations.