gitnexus-refresh-on-stale

To automate GitNexus index refresh for stale repositories, you can use a skill that checks the index status and triggers a refresh automatically when staleness is detected, eliminating manual monitoring.

A GitNexus index becomes stale when underlying repository data changes but the index is not updated. Automating the staleness check ensures your local skills remain synced without manual intervention.

To sync local skills after refreshing a stale GitNexus index, use a tool that automatically copies newly generated skills from `.claude/skills/gitnexus` to `.agents/skills/gitnexus`.

Yes, you can use bash scripts alongside GitNexus command-line tools to automatically check if your index is stale and trigger the necessary refresh and skill synchronization actions.

The best way to maintain up-to-date GitNexus skill sets is to automate the detection of stale indexes and trigger immediate refreshes and skill syncs, ensuring your local environment is always current.