cpoepke/redex
plugins/toondex/skills/redex/SKILL.md
Update existing index.toon with changes. Detects new/deleted/modified folders and updates the semantic folder index.
tools
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add cpoepke/toon-dex redexInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 3:24 PM249.9s1 file scanned
SKILL.md
- name:
- redex
- description:
- Update existing index.toon with changes. Detects new/deleted/modified folders and updates the semantic folder index.
/redex - Update Existing Index
WHEN THIS SKILL IS INVOKED, IMMEDIATELY BEGIN EXECUTING THE STEPS BELOW. DO NOT JUST EXPLAIN THE PROCESS - ACTUALLY RUN THE COMMANDS AND PERFORM THE ANALYSIS.
This skill updates existing index.toon files to reflect codebase changes.
CRITICAL: Execution Instructions
When this skill loads, you MUST:
- START IMMEDIATELY with Step 1 below (detect changes)
- EXECUTE each step - run git commands, read files, analyze folders
- DO NOT just describe what the skill does - DO IT NOW
- ONLY show documentation if the user explicitly asks for help
If index.toon does not exist, tell the user to run /toondex first.
Implementation Steps (Execute Now)
BEGIN EXECUTION IMMEDIATELY:
When to Use
Run /redex when:
- Files or folders have been added, deleted, or significantly modified
- You see a suggestion that the index may be outdated
- You want to refresh folder summaries
What It Does
- Detects changes since last index via git
- Identifies what changed: New folders, deleted folders, modified folders
- Re-analyzes only the changed folders
- Presents a diff showing old vs new summaries
- Updates the affected
index.toonfiles
Process (EXECUTE THESE STEPS NOW)
Step 1: Detect Changes (DO THIS NOW)
RUN these git commands to find changes since the last index.toon commit:
LAST_REF=$(git log -1 --format="%H" -- index.toon)
git diff --name-only $LAST_REF..HEAD
Parse the output to identify changed folders.
Step 2: Identify What Changed (DO THIS NOW)
Categorize the changes:
- New folders: Folders created since last index
- Deleted folders: Folders that no longer exist
- Modified folders: Folders with file changes
Step 3: Re-analyze Changed Folders (DO THIS NOW)
For EACH changed folder, IMMEDIATELY:
- Read 3-5 representative source files from that folder
- Generate a 1-3 sentence behavioral summary
- Calculate confidence score (0.0-1.0)
- Compare with the old summary from existing index.toon
###Step 4: Present Diff (DO THIS NOW)
SHOW the user this diff format:
index.toon changes:
MODIFIED:
src/auth:
old: "JWT-based authentication."
new: "Clerk-based authentication. Role middleware." [0.8]
NEW:
src/analytics: "PostHog integration for user tracking." [0.7]
DELETED:
src/legacy (folder no longer exists)
Apply changes? [Y/n]
Step 5: Update Index Files
After user approval:
- Update the relevant
index.toonfiles (only those with changes) - Preserve order for unchanged entries
- Insert new entries at appropriate priority position
Auto-Detection
The SessionStart hook automatically checks if the index is outdated and may suggest running /redex when:
- Change score exceeds threshold (see detect-changes.sh)
- New top-level folders exist (not in index)
- Indexed folders are deleted
- Many files changed in indexed folders
- More than 7 days since last index
When you see: "PROPOSE_REINDEX: index.toon may be outdated...", consider running /redex.
Examples
Updating After Code Changes
User: /redex
Claude: Detecting changes since last index...
Found changes in 3 folders:
- src/components (15 files modified)
- src/api (new folder)
- src/legacy (deleted)
Re-analyzing...
index.toon changes:
MODIFIED:
src/components:
old: "UI components using shadcn."
new: "UI components using shadcn. Added form components with validation." [0.9]
NEW:
src/api: "REST API endpoints. Express routes with middleware." [0.8]
DELETED:
src/legacy
Apply changes? [Y/n]
When No Changes Detected
User: /redex
Claude: No significant changes detected since last index. Your index.toon is up to date!
Tips
- Run
/redexregularly to keep the index current - The SessionStart hook will remind you when the index is stale
- If you see low confidence scores during update, review those summaries
- New folders are added at the end by default - you can manually reorder them for priority
See Also
/toondex- Create initial index/toondex --stats- View usage statistics (requires TOONDEX_DEBUG=1)
For full documentation, see the main toondex skill or plugins/toondex/skills/toondex/SKILL.md.
Related Skills
cpoepke/toondex
development
VerifiedTrustedCommunity
Semantic folder index for codebase navigation. Commands: /toondex (create), /redex (update). IMPORTANT: If you see "PROPOSE_REINDEX" in your context (injected by SessionStart hook), when the user sends their next message, briefly ask if they want you to run /redex first or if you should continue answering their question. "Oh, I see you've discovered my meticulously organized archive."
SKILL.mdUpdated Apr 25, 2026
cpoepke/stats
development
VerifiedTrustedCommunity
Show ToonDex debug mode usage statistics. Tracks hook fires, index.toon reads, and effectiveness metrics.
SKILL.mdUpdated Apr 25, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026