Smart Doc Keeper

Merges new documentation into existing Markdown files while preserving original content and structure.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/adriangmrraa/MultiAgents-Platform-ROI --skill smart-doc-keeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Smart Doc Keeper
Source: https://github.com/adriangmrraa/MultiAgents-Platform-ROI/tree/main/.agent/skills/Doc_Keeper
Command: npx skills add https://github.com/adriangmrraa/MultiAgents-Platform-ROI --skill smart-doc-keeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents accidental loss of documentation and preserves historical content by enforcing a non-destructive merge protocol when updating Markdown files after code or skill changes. It reduces risk during maintenance by requiring full-file reads, anchor-aware insertion, and integrity checks before any write.

Core Features & Use Cases

  • Full-file Read-before-Write: Always reads the entire target Markdown document before making any modifications to ensure no unseen content is overwritten.
  • Anchor Detection & Intelligent Fusion: Locates logical insertion points (headings, tables, lists) and applies one of three strategies—Append for changelogs, Injection for lists/tables, or Deprecation for replacements—so new content is merged cleanly.
  • Safety & Verification: Runs integrity checks to detect large-length reductions, missing headers, or structural changes that could indicate destructive edits.
  • SKILL.md Special Handling: Preserves YAML frontmatter of SKILL.md files and only modifies body sections when explicitly requested.
  • Use Case Examples: Add a "Panic Button" section to docs/CHATS_LOGIC.md, insert new API endpoints into API_REFERENCE.md tables, or append changelog entries to REPORT_MASTER.md without losing previous content.

Quick Start

Ask Smart Doc Keeper to merge the new "Panic Button" documentation into docs/CHATS_LOGIC.md using the non-destructive fusion protocol.

Frequently Asked Questions about Smart Doc Keeper

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

FAQPage Schema
How do I merge updated documentation into existing Markdown files without losing the original content?

To merge documentation without losing original content, use a non-destructive merge protocol that reads the full Markdown file before writing. This ensures no unseen content is overwritten by applying anchor-aware insertion and integrity checks.

What is the best way to append new API endpoints to Markdown reference tables without breaking the structure?

The best way to append endpoints to Markdown reference tables is using an intelligent injection strategy that detects tables as anchors. This safely inserts new API endpoints into the existing structure while preserving the surrounding formatting and data.

Can I update SKILL.md files and preserve the YAML frontmatter during the edit?

Yes, you can update SKILL.md files and preserve YAML frontmatter by using a merge protocol that explicitly protects frontmatter. It will only modify body sections when explicitly requested, leaving the metadata headers intact.

How do you prevent destructive edits when updating changelog Markdown files?

Destructive edits during changelog updates are prevented by running safety checks that detect large-length reductions or missing headers. An append strategy adds new entries while verifying structural integrity before writing to the file.

When should I use a non-destructive merge protocol for repository documentation maintenance?

You should use a non-destructive merge protocol for repository documentation maintenance when updating changelogs, API references, or SKILL.md files after code changes. It prevents accidental loss of historical content by enforcing full-file reads before any modifications.