npx claudepluginhub alirezanasseh/nogrep --plugin nogrepUpdate stale nogrep context nodes based on recent changes. ## Step 1: Check for stale nodes Run the validation script to find stale nodes: If there are no stale nodes, tell the user: > All nogrep context nodes are up to date. Nothing to update. If the validation fails because no index exists, tell the user: > No nogrep index found. Run `/nogrep:init` first. ## Step 2: Identify changed files Run git diff to find recently changed files: If no git is available, tell the user you'll re-analyze all stale nodes based on hash mismatch. ## Step 3: Map changes to affected nodes Read `...
/updateUpdates beads issue fields: status, priority, assignee, title, or description. Accepts [issue-id] [value]; prompts interactively if missing. Applies via tool and shows updated issue.
/updateReflects on project changes, investigates impacts, updates stable llmdoc docs in must/, guides/, reference/, syncs index.md, and reports reflection path with changed files.
/updateUpdates statusLine.command path in ~/.claude/settings.json to latest claude-dashboard plugin version from cache. Shows previous/new paths and restart reminder.
/updateChecks metaswarm plugin version against marketplace, applies updates if available (auto for marketplace, migration guide for npm), and verifies skills load correctly.
/updateChecks PDF Playground plugin version, updates to latest via claude plugin update if needed, confirms change, and prompts restart of Claude Code.
/updateUpdates VBW plugin to the latest cached version with automatic cache refresh. Use --check to read current installed version without updating.
Update stale nogrep context nodes based on recent changes.
Run the validation script to find stale nodes:
node "${CLAUDE_PLUGIN_ROOT}/scripts/validate.js" --format json
If there are no stale nodes, tell the user:
All nogrep context nodes are up to date. Nothing to update.
If the validation fails because no index exists, tell the user:
No nogrep index found. Run
/nogrep:initfirst.
Run git diff to find recently changed files:
git diff origin/main --name-only 2>/dev/null || git diff HEAD~10 --name-only 2>/dev/null || echo "NO_GIT"
If no git is available, tell the user you'll re-analyze all stale nodes based on hash mismatch.
Read .nogrep/_registry.json to map changed files to their context nodes.
For each stale node from Step 1:
## Manual Notes contentsrc_paths frontmatternode "${CLAUDE_PLUGIN_ROOT}/scripts/trim.js" <source_file_paths>
For each stale node, analyze the trimmed source and generate an updated context node.
Read .nogrep/_taxonomy.json for allowed tag values.
Return JSON only, no prose, no markdown fences:
{
"purpose": "2-3 sentences MAX. Business intent, not technical description.",
"public_surface": ["list of exported functions/routes/events other domains use"],
"does_not_own": ["what this module delegates elsewhere, with → target domain"],
"external_deps": [{"name": "lib", "usage": "what it's used for"}],
"tags": {
"domain": [],
"layer": [],
"tech": [],
"concern": [],
"type": []
},
"keywords": ["terms a developer would search to find this domain"],
"gotchas": ["max 5 non-obvious behaviors, footguns, or constraints"]
}
Rules:
Combine all updated node results with any unchanged nodes. Pipe the full set as JSON to the writer:
echo '<json_input>' | node "${CLAUDE_PLUGIN_ROOT}/scripts/write.js" --root .
The writer automatically preserves ## Manual Notes sections from existing files.
Tell the user which nodes were updated and suggest reviewing the changes:
Updated N nogrep context nodes. Run
git diff .nogrep/to review changes.