Help us improve
Share bugs, ideas, or general feedback.
From jd
Audit a Johnny.Decimal system by comparing the JDex against the actual folder structure, flagging mismatches, orphaned entries, and undocumented folders. Use this skill when the user wants to verify their JD system, check for inconsistencies, sync their JDex with the filesystem, or says things like "audit my JDex," "check my system," "sync JDex," "verify my JD system," "is my JDex up to date," or "find orphaned folders."
npx claudepluginhub ngerakines/jd --plugin jdHow this skill is triggered — by the user, by Claude, or both
Slash command
/jd:jd-jdex-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill compares a system's JDex (the authoritative index) against the
Scaffolds, validates, and maintains Johnny.Decimal directory structures for project documentation using Python scripts for init, validation, indexing, area addition, and file classification/migration.
Runs 7-phase Obsidian vault audit: structural scan, duplicate detection, link integrity, frontmatter audit, MOC review, cross-agent checks, health report.
Audits Claude Code workspaces (walnuts) for maintenance issues like stale tasks, orphan folders, v2 remnants, and unsaved sessions. Surfaces issues one at a time with recommended fixes.
Share bugs, ideas, or general feedback.
This skill compares a system's JDex (the authoritative index) against the actual folder structure on disk, identifying mismatches and suggesting fixes.
Check common locations:
~/Library/Mobile Documents/com~apple~CloudDocs/JD/ (iCloud Drive)~/Documents/JD/~/JD/If the user specifies a system code (e.g., "audit my P10 system"), target that specific system. Otherwise, list all available systems and ask which to audit.
Read the JDex file at:
SYS/00-09 */00 */00.00 *JDex*
Parse it into a structured list of areas, categories, and IDs. Each entry should capture:
List all folders to depth 3 under the system root. Parse folder names to extract AC.ID addresses, area ranges, and category numbers.
Run three checks:
JDex entries that have no corresponding folder on disk.
These indicate either:
Folders on disk that have no corresponding JDex entry.
These indicate either:
JDex entries whose description doesn't match the folder name, or folders
whose name doesn't follow the expected AC.ID Description format.
For categories that use +SUB extensions:
+SUB categories typically have an index file (e.g., 51.01 Open-source project index.md). Find these by looking for files matching *.md at the category
or ID level that contain +SUB listings.
+NNNN or +CODE folders within the IDPresent a clear audit report to the user:
## JDex Audit: [System name]
**Audit date:** YYYY-MM-DD
**JDex location:** [path]
**System root:** [path]
### Summary
| Check | Count |
|-------|-------|
| JDex entries | N |
| Filesystem folders | N |
| Orphaned JDex entries | N |
| Undocumented folders | N |
| Name mismatches | N |
| +SUB index issues | N |
### Orphaned JDex Entries (in JDex but no folder)
| AC.ID | Description | Suggested Action |
|-------|-------------|-----------------|
| 11.05 | Home improvement | Create folder or remove from JDex |
### Undocumented Folders (folder exists but not in JDex)
| Folder | Path | Suggested Action |
|--------|------|-----------------|
| 11.08 Garage storage | 10-19/11/11.08 | Add to JDex |
### Name Mismatches
| AC.ID | JDex says | Folder says | Suggested Action |
|-------|-----------|-------------|-----------------|
| 11.03 | Home insurance | Homeowners insurance | Reconcile names |
### +SUB Index Issues
| Category | Issue | Details |
|----------|-------|---------|
| 51.01 | Missing from index | +0004 folder exists, not in index |
After presenting the report, offer to fix issues:
If the user requests it, offer to regenerate the JDex entirely from the folder structure:
Warning: Regeneration loses any JDex entries that don't have corresponding folders. Always confirm before proceeding.
When auditing multiple systems: