Gitnexus Refresh On Stale

Refresh GitNexus indexing and regenerate local GitNexus skills when repository status is stale. Use when `npx gitnexus status` reports stale/outdated index state, or when you need to sync newly generated `.claude/skills/gitnexus` into `.agents/skills/gitnexus` with overwrite behavior. Use when this capability is needed.

tomevault-io Updated

File contents

GitNexus Refresh On Stale

Run this skill from the repository root.

Workflow

  1. Check index status.
npx gitnexus status
  1. If status contains stale (case-insensitive), run:
npx gitnexus analyze
  1. If .claude/skills/gitnexus exists after analyze, replace .agents/skills/gitnexus with it.
  • Delete existing .agents/skills/gitnexus when present.
  • Move .claude/skills/gitnexus to .agents/skills/gitnexus.
  1. If status is not stale, do not run analyze.

Script

Use the bundled script for deterministic behavior:

bash .agents/skills/gitnexus-refresh-on-stale/scripts/refresh_gitnexus_skills.sh

The script performs all steps above and prints what it changed.


Source: ML4ITS/TimeVQVAE — distributed by TomeVault.

tomevault-io/skills-registry/tree/main/ml4its--timevqvae--timevqvae commit e86ba8250d

Frequently asked questions

npx skillmds@latest add tomevault-io/gitnexus-refresh-on-stale