agent-notepad-prune

Merge duplicate notes and archive outdated entries in the .codex/notes tree.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/MithrilMan/neomithril-ui --skill agent-notepad-prune
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-notepad-prune
Source: https://github.com/MithrilMan/neomithril-ui/tree/main/.codex/skills/agent-notepad-prune
Command: npx skills add https://github.com/MithrilMan/neomithril-ui --skill agent-notepad-prune

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile contradictions and remove stale noise in the .codex/notes tree. Use at phase boundaries or when conflicts appear to merge duplicates, mark superseded notes, archive outdated entries, and keep indexes accurate.

Core Features & Use Cases

  • Keeps memory tree trustworthy by merging duplicates and archiving stale notes.
  • Resolves contradictions with evidence-based selections and status tagging.
  • Maintains accurate, navigable indexes across branches for fast lookup.

Quick Start

Identify conflicted or obsolete notes in .codex/notes and apply the prune workflow to merge duplicates, archive superseded entries, and refresh the index.

Frequently Asked Questions about agent-notepad-prune

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prune stale notes and reconcile contradictions in my memory tree?

You can prune stale notes by applying a reconcile workflow to the .codex/notes tree, which merges duplicates, archives outdated entries, and resolves contradictions using evidence-based selections and status tagging.

What is the best way to merge duplicate notes across branches without losing data?

Merging duplicate notes across branches is handled safely through non-destructive merges that preserve historical references, mark superseded entries, and update indexes to keep the memory tree navigable.

When should I run a memory prune and reconcile workflow on my notes?

You should run a memory prune at phase boundaries or when conflicts appear in the .codex/notes tree, ensuring outdated entries are archived and indexes remain accurate for fast lookup.

Does pruning outdated notes delete my historical references permanently?

Pruning outdated notes does not delete history permanently; the process uses non-destructive merges and archiving to preserve historical references while marking superseded entries with clear status tags.

How do outdated notes and duplicates slow down memory lookup, and how does archiving fix it?

Outdated notes and duplicates clutter the .codex/notes tree and slow down memory lookup, but archiving stale entries and updating indexes across branches restores fast and trustworthy access.