skills.rest
hossam7amdy
hossam7amdyCOMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

Merge delta specifications from change sets into main specification files.

Updated Jan 23, 2026
Search Tags:#automation#CLI#openspec#delta#merging#specs#version-control
One-click install
npx skills add https://github.com/hossam7amdy/easy-auth --skill openspec-sync-specs-hossam7amdy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/hossam7amdy/easy-auth/tree/main/.agent/skills/openspec-sync-specs
Command: npx skills add https://github.com/hossam7amdy/easy-auth --skill openspec-sync-specs-hossam7amdy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Read delta specs from openspec/changes/<change-name>/specs
  • Apply changes to main specs at openspec/specs
  • Supports ADDED, MODIFIED, REMOVED, and RENAMED blocks
  • Performs intelligent merging while preserving unrelated content
  • Idempotent operation; repeated runs have no additional changes

Quick Start

To start syncing, ensure the openspec CLI is installed. List available delta changes with openspec list --json, then run openspec sync <change-name> to merge the delta specs into the main specs. The command is idempotent; running it again will not duplicate changes.

Frequently Asked Questions about openspec-sync-specs

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

FAQPage Schema
How do I sync delta specs into my main specs repository?▼

To sync delta specs, use the openspec CLI to read changes from openspec/changes/<name>/specs and apply them to openspec/specs. This merges ADDED, MODIFIED, REMOVED, and RENAMED sections into the main specs.

What happens to unrelated content when merging delta specifications?▼

Merging delta specifications preserves all unrelated content in the main specs repository. The operation only applies the specific ADDED, MODIFIED, REMOVED, or RENAMED blocks defined in the delta spec.

Are repeated spec sync operations safe for my repository?▼

Yes, spec sync operations are completely idempotent. Repeated runs produce no additional changes or duplicated content, guaranteeing a deterministic merge every time you execute the command.

Do I need to archive a change before syncing its delta specs?▼

No, you do not need to archive a change before syncing. You can use this specifically to update main specs with changes from a delta spec without archiving the change itself.

Can I use openspec sync to rename or remove spec sections?▼

Yes, openspec sync fully supports RENAMED and REMOVED blocks. It intelligently processes these delta spec instructions to update or delete the corresponding sections in the main specification files.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

openspec-archive-change

Archive completed OpenSpec change directories after validating artifacts and tasks.

Official
Advanced
xiayu519xiayu519
63

openspec-archive-change

Archive completed OpenSpec changes to the archive directory after validation gates pass.

Community
Advanced
tungnguyen10tungnguyen10

openspec-sync-specs

Merge delta specification changes into main project spec files.

Community
Intermediate
dezkareiddezkareid
6

openspec-sync-specs

Merge delta specs into main specs using openspec CLI.

Community
Advanced