merge-docs
From the author
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.
Install
npx skills add serpro69/claude-toolbox --skill merge-docs -a claude-code
Installs to .claude/skills/merge-docs/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 78
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- mergemembranedev/application-skillsMerge integration. Manage data, records, and automate workflows. Use when the user wants to interact with Merge data.Other★ 270
- doc-consolidationathola/claude-night-marketMerges ephemeral report and analysis artifacts into permanent documentation. Use when LLM-generated markdown files have accumulated and need consolidation.Other★ 343
- reverse-documentvibeeval/vibecosystemGenerate design docs, ADRs, and concept docs from existing code by reverse engineering intentDesign★ 540
- designvladikk/modularityDesigns modular high-level architectures from functional requirements and produces design documents for each module. Use when designing a new system, creating architecture documentation, or producing module-level design specs with integration contracts and test specifications.Design★ 566
- microsoft-docssandbaseai/sandbase-skillsResearch and evaluate microsoft docs with current authoritative sources, provenance, and explicit evidence gaps. Use when the user asks for microsoft docs findings or verification.Science★ 203
- alignmentOvid/paadUse when verifying that requirements/specs/PRDs and their implementation plans match — before starting work, after a spec or plan update, or when suspecting coverage gaps, scope creep, or design drift between intent and action documents. Needs both documents; not for checking code against a spec.Design★ 143
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in