merge-docs SKILL.md skillA
merge-docs from serpro69/claude-toolbox is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add serpro69/claude-toolbox/merge-docs@git:20260910.562e70aPins git:20260910.562e70a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- serpro69/claude-toolbox
- Path
kodex-plugin/skills/merge-docs/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260910.562e70a, committed Sep 10, 2026
- First version recorded
- Apr 27, 2026
- Size
- 1,318 bytes
- Repository stars
- 155
- License
- a license file GitHub does not identify
Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- codex: tool-name mapping applied. See .codex/scripts/session-start.sh --> # Merge Design Documents **Goal: Produce a single, unified set of feature docs from two separate designs for the same feature.** ## Conventions - **Read capy knowledge base conventions** at [shared-capy-knowledge-protocol.md](shared-capy-knowledge-protocol.md). ## When to Use You have two feature directories under `/docs/feat/wip/` for the same feature — each with its own design, implementation plan, and task list — and you need to combine them into one coherent set of docs. ## Workflow **Mandatory order — grounding before merging.** The flow below is strictly sequential. Do not categorize sections, surface contradictions, or write merged content until you have read both feature directories fully and built a codebase-grounded mental model. Merging without grounding produces decisions based on prose clarity rather than codebase reality — the wrong tiebreaker. See [merge-process.md](./merge-process.md) for the detailed steps.
Read the whole file at its exact version.
How to install
mdr add serpro69/claude-toolbox/merge-docs@sha256:8f2cc6725b753027The line at the top of this page pins the label git:20260910.562e70a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_b6av32molaygdvbz)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Apr 27, 2026 and Sep 10, 2026, about one every 45 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260910.562e70a latest | 2026-09-10 | 562e70a | 1,318 B | A | view · diff |
| git:20260605.a4fab48 | 2026-06-05 | a4fab48 | 1,313 B | A | view · diff |
| git:20260427.c1181c6 | 2026-04-27 | c1181c6 | 1,392 B | A | view · diff |
| git:20260427.fa402ef | 2026-04-27 | fa402ef | 1,307 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1318 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
serpro69/claude-toolbox · 155 stars · license a license file GitHub does not identify · pushed 2026-11-04 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_b6av32molaygdvbz GET https://markdownregistry.com/api/v1/resolve?ref=serpro69/claude-toolbox/merge-docs GET https://markdownregistry.com/api/v1/blob/8f2cc6725b753027d9a5fc4acf3978a18f62269bd11d4951115680e04d204dda
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from serpro69/claude-toolbox
Every file in serpro69/claude-toolbox