Skill

mem-fix

Fixes knowledge base issues from mem-audit: broken links, orphan notes, missing indexes, stale rebuilds. Dry-run previews changes before atomic application.

developer-tools

documentation

npx claudepluginhub z-m-huang/cc-obsidian-mem

Tool Access

This skill is limited to using the following tools:

mcp__obsidian-mem__mem_auditmcp__obsidian-mem__mem_fixmcp__obsidian-mem__mem_read

Preview

Apply fixes for issues detected in your Claude Code knowledge base.

SKILL.md

Similar Skills

cache-components

139.2k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Parent Repo Stars10

Parent Repo Forks3

Last CommitJan 22, 2026

Actions

View Source View Plugin View on GitHub View README

Memory Fix Skill

Apply fixes for issues detected in your Claude Code knowledge base.

When to Use

After running /mem-audit and finding issues
To clean up broken links
To add missing parent links to orphan notes
To create missing category indexes
To rebuild stale indexes

Usage

/mem-fix project:my-project
/mem-fix project:my-project dryRun:true
/mem-fix project:my-project fixCategories:broken_link,orphan_note

Workflow

Run Audit First
- Call mem_audit to get current issues
- Present summary: X errors, Y warnings, Z info
Collect Confirmation
- Group issues by category
- For each category with issues, ask: "Fix all N [category] issues?"
- Show examples (first 3-5) before asking for confirmation
Apply Fixes
- Use dryRun: true first to preview changes
- Then apply confirmed fixes with dryRun: false
Report Results
- Show what was fixed successfully
- Show what failed and why
- Suggest re-running audit to verify

Fix Types

Category	Fix Type	Auto-Fixable
`broken_link`	Remove the broken wikilink	Yes
`orphan_note`	Add parent link to frontmatter	Yes
`missing_index`	Create category index file	Yes
`supersession_inconsistent`	Update frontmatter (may need manual input)	Partial
`index_stale`	Rebuild project index	Yes
`invalid_frontmatter`	Add missing fields (except title)	Partial

Output Format

Dry Run

# Dry Run Results

**Would fix**: 8/10

## Successful

- `broken_link-abc123`: Would remove link [[old-note]]
  - link_removed: Removed broken link [[old-note]]

## Failed

- `supersession_inconsistent-def456`: No suggested fix available

---
Run again with `dryRun: false` to apply these changes.

After Applying

# Fix Results

**Fixed**: 8/10

## Successful

- `broken_link-abc123`: Removed link [[old-note]]
  - link_removed: Removed broken link [[old-note]]

## Failed

- `supersession_inconsistent-def456`: No suggested fix available

Safety Features

Dry run by default: Always preview changes first
Atomic writes: Files are written atomically to prevent corruption
TOCTOU protection: Checks if files changed since audit before applying fixes
Individual results: Each fix reports success/failure independently

Follow-up Actions

After fixing, suggest:

/mem-audit to verify all issues are resolved
Review any failed fixes manually