skills.rest
martinsson
martinssonCOMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

Merge delta specs from openspec/changes into main specs using ADDED, MODIFIED, REMOVED, and RENAMED rules.

Updated Feb 12, 2026
Search Tags:#automation#merge#openspec#guardrails#delta-specs#main-specs#spec-merge
One-click install
npx skills add https://github.com/martinsson/checkin-automation --skill openspec-sync-specs-martinsson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/martinsson/checkin-automation/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/martinsson/checkin-automation --skill openspec-sync-specs-martinsson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges delta specifications into main specifications, enabling changes to be applied without archiving separate revisions.

Core Features & Use Cases

  • Intelligent merging: updates main specs using ADDED, MODIFIED, REMOVED, and RENAMED rules with preserved existing content.
  • Delta-driven workflow: reads delta specs from openspec/changes and updates openspec/specs accordingly.
  • Guardrails & idempotency: ensures changes are applied safely and can be re-run without duplicating results.

Quick Start

Operate the delta-merge workflow by selecting a change and applying its delta to the corresponding main specs.

Frequently Asked Questions about openspec-sync-specs

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

FAQPage Schema
How do I merge delta specs into main specs without losing existing content?▼

You can merge delta specs into main specs by applying ADDED, MODIFIED, REMOVED, and RENAMED rules, which updates the main specifications while preserving all existing content that isn't targeted for changes.

What are delta specs and when do I need to merge them?▼

Delta specs are incremental change definitions stored in openspec/changes. You need to merge them when you want to propagate these specific changes into your main specs located in openspec/specs without archiving separate revisions.

How do I apply spec changes safely using a delta-driven workflow?▼

You can apply spec changes safely by running an automated delta-merge workflow that uses built-in guardrails to ensure changes are applied correctly and idempotently, preventing duplicate results on re-runs.

Can I re-run a spec merge without creating duplicate changes?▼

Yes, the spec merge process is idempotent, meaning you can re-run the merging operation multiple times and it will produce the exact same result without duplicating changes or overwriting unintended content.

What is the best way to propagate RENAMED or REMOVED rules from changes to specs?▼

The best way to propagate RENAMED or REMOVED rules is to use an automated delta-merge tool that reads these rules directly from your openspec/changes directory and applies them to the main specs safely.

Related Skills

Explore More Product & Management Skills→
AdJIaAdJIa

openspec-sync-specs

Merge delta spec changes into main OpenSpec specs idempotently.

Community
Advanced
jerome-benoitjerome-benoit
57

openspec-sync-specs

Merge delta specifications into main specs with guardrails for review.

Community
Advanced
psaccpsacc

openspec-sync-specs

Merge delta specification changes into main openspec spec files.

Community
Advanced
carlosapgomescarlosapgomes

openspec-sync-specs

Merge delta specs into main specs with ADDED, MODIFIED, REMOVED, and RENAMED changes.

Community
Advanced