merge-reference-docs

To merge markdown reference files, use the merge-reference-docs skill to combine external guides into project-specific documentation while preserving the target structure and frontmatter. It harmonizes best practices across multiple documents to maintain a single source of truth for project governance.

Consolidating external reference guides with existing agent definitions involves merging the reference markdown into your local project files. This skill normalizes terminology and rules across documents, extending your agent definitions with consistent guidance without losing project-specific structure.

Yes, you can preserve frontmatter when merging markdown documentation. The merge process specifically protects the target document's frontmatter and structural formatting while optionally incorporating the content from the external reference files during the consolidation.

Keeping a single source of truth for project rules and skills requires harmonizing best practices across multiple documents. By merging external reference files into your target project documentation, you normalize terminology and align guidelines to prevent conflicting rule definitions.

Yes, the markdown merge process supports multiple reference files at once. You can provide one target file followed by multiple reference files as inputs, allowing you to consolidate several external best-practice guides into a single project document simultaneously.