skills.rest
a2mus
a2musCOMMUNITY
Explore all skills by this author →
GitHub

speckit-update-upstream

Sync a forked spec-kit repository with upstream changes while preserving identity files.

Updated Apr 7, 2026
Search Tags:#git#merge#sync#spec-kit#upstream#fork
One-click install
npx skills add https://github.com/a2mus/smart-da3m --skill speckit-update-upstream
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-update-upstream
Source: https://github.com/a2mus/smart-da3m/tree/main/.agents/skills/speckit-update-upstream
Command: npx skills add https://github.com/a2mus/smart-da3m --skill speckit-update-upstream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a forked spec-kit repository up to date with upstream changes while avoiding accidental overwrites of local identity customizations, reducing manual merge work and merge conflicts.

Core Features & Use Cases

  • Intelligent Syncing: Fetches upstream updates and analyzes diffs file-by-file to determine safe merges.
  • Customization Preservation: Preserves identity and local customization files while applying updates to templates, skills, and workflows.
  • Use Case: Maintain a customized spec-kit fork across team members by regularly pulling upstream fixes and feature updates without losing local branding or identity files.

Quick Start

Synchronize my fork with the upstream spec-kit repository, analyze file-level diffs, and merge updates while preserving local identity customizations.

Frequently Asked Questions about speckit-update-upstream

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

FAQPage Schema
How do I sync a forked spec-kit repository with upstream without losing local customizations?▼

Syncing a forked spec-kit repository requires fetching upstream changes and performing file-by-file diff analysis to intelligently merge updates. This preserves local identity customizations while safely applying template, skill, and workflow updates.

What is the best way to merge upstream git changes into a fork while preserving identity files?▼

Merging upstream git changes safely requires analyzing file-level diffs to protect identity files. This targeted approach updates templates and workflows while preventing accidental overwrites of local branding and custom project configurations.

Do I need standard git tooling and both remotes configured to sync a spec-kit fork?▼

Yes, syncing a spec-kit fork requires standard git tooling and access to both fork and upstream git remotes. The project must also contain a .specify directory to correctly target templates, skills, and workflow files during maintenance.

Can I selectively apply upstream updates to templates and skills without overwriting local workflow files?▼

Yes, you can selectively apply upstream updates by analyzing file-by-file diffs during the merge process. This intelligent syncing updates templates and skills while explicitly preserving custom workflow files and local identity configurations.

Why does merging upstream spec-kit changes cause conflicts in local identity files?▼

Merging upstream spec-kit changes causes conflicts because standard git merges lack file-level awareness of local identity files. Intelligent syncing solves this by analyzing diffs and explicitly preserving customized identity files during the update process.

Related Skills

Explore More Software Engineering Skills→
heyJordanParkerheyJordanParker
20

naming

Evaluate identifiers to enforce consistent naming across codebases.

Community
Basic
dnvitidnviti
11

git-publish

Merge develop into main and push both branches to origin.

Community
Intermediate
cloud-native-toolscloud-native-tools

code-review

Standardize code reviews with git-delta diff visualization and structured feedback.

Official
Advanced
alangebalangeb

git

Automate git worktree synchronization via rebase and fast-forward merges.

Community
Advanced