pull-upstream

Pull ddd-core changes into a fork's core/ subtree and validate the build.

Updated May 25, 2026
One-click install
npx skills add https://github.com/dddwa/ddd-core --skill pull-upstream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-upstream
Source: https://github.com/dddwa/ddd-core/tree/main/.claude/skills/pull-upstream
Command: npx skills add https://github.com/dddwa/ddd-core --skill pull-upstream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the guesswork and risk of updating a ddd-core-based conference fork by guiding you through a safe subtree pull, then verifying the fork still builds after the update.

Core Features & Use Cases

  • Subtree-based upstream sync: Pulls the latest ddd-core changes into the fork’s core/ subtree.
  • Conflict detection with guardrails: Checks for conflicts and stops to force manual resolution when the fork has edited files inside core/.
  • Post-pull verification: Runs dependency install and a build (pnpm nx build website) to catch contract drift (e.g., manifest/theme field changes).

Quick Start

Run pull-upstream from inside your fork repository that contains both core/ and conference/.

Frequently Asked Questions about pull-upstream

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

FAQPage Schema
How do I sync changes from an upstream monorepo into a forked subtree?

Syncing upstream changes into a forked subtree involves executing a git subtree pull to fetch the latest core updates, then running dependency installation and build validation to ensure the fork still compiles without contract drift.

What happens if there are conflicts during a git subtree pull from upstream?

During a git subtree pull, conflict detection checks for edits inside the core directory and stops the upstream sync to force manual conflict resolution, ensuring your fork-owned conference content remains unedited upstream.

How does build verification work after pulling upstream changes into a monorepo?

Build verification after an upstream sync runs dependency installation followed by an nx build and typecheck validation to catch contract drift, ensuring the fork still compiles before finalizing the merge.

Does upstream sync work if my fork has modified files inside the core subtree?

Upstream sync works but will halt if your fork has modified files inside the core subtree, surfacing conflicts to force manual resolution and preventing upstream overwrites of your local changes.

Why does pulling upstream changes require a clean working tree?

Pulling upstream changes requires a clean working tree to safely execute the subtree pull and accurately surface merge conflicts, preventing untracked local modifications from interfering with the post-merge build verification.

What is the best way to update a fork's core subtree while keeping conference content fork-owned?

The best way to update a core subtree while keeping conference content fork-owned is a guided subtree pull that isolates upstream changes to the core directory and stops to enforce manual resolution if upstream files are edited.