openspec-sync-specs
From the author
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
Install
npx skills add MemeMeow-Studio/MemeMeow --skill openspec-sync-specs -a claude-code
Installs to .claude/skills/openspec-sync-specs/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
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 88
Security100
Provenance77
Maintenance100
Licence100
Adoption50
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.
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.Writing★ 1.3K
- openspec-archive-changeMemeMeow-Studio/MemeMeowArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.Productivity★ 1.3K
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.Productivity★ 1.3K
- vibe-spec-syncash1794/vibe-engineeringKeeps specification documents and code in agreement. Audit mode finds every divergence when an implementation is claimed complete; sync mode detects spec drift in staged changes and updates the spec after user approval, so each commit is a reconciled snapshot of spec, tests, and code. Use when an implementation is claimed complete against a spec, before committing changes that may drift from the spec, or after approving decisions that must flow back into it.Planning★ 165
- review-specserpro69/claude-toolboxUse after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.Planning★ 154
- documentation-syncomergocmen/vibe-coder-kitAfter any significant code change — new feature, API modification, config change, or architectural refactor — run this skill to identify which documentation files are now stale and update them. Keeps docs and code from drifting apart.Planning★ 97
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in