ce:sync-upstream

Detect upstream repository updates and generate structured sync analysis reports.

6|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Jerrylalala/compound-engineering --skill ce-sync-upstream-jerrylalala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce:sync-upstream
Source: https://github.com/Jerrylalala/compound-engineering/tree/main/plugins/compound-engineering/skills/ce-sync-upstream
Command: npx skills add https://github.com/Jerrylalala/compound-engineering --skill ce-sync-upstream-jerrylalala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tracking changes across multiple upstream repositories is tedious and noisy, making it hard to decide which updates are worth integrating into your fork or downstream project. ## Core Features & Use Cases - Multi-Repo Update Detection: Scans multiple upstream repositories for the last 30 days of commits and releases using git-native, GitHub API, or releases-only strategies. - Noise Filtering & Relevance Analysis: Filters out chore commits, dependency bumps, and merge noise, then rates each change as high, medium, or low relevance with justification. - Structured Reports: Writes a dated Markdown report with YAML frontmatter, summary tables, and prioritized integration recommendations to docs/sync-reports/. - Use Case: You maintain a fork of several open-source projects. Run the command to get a single report of all relevant upstream changes from the past month, then choose to discuss items, create an integration plan, or merge directly. ## Quick Start Ask the assistant to run /ce:sync-upstream to check all configured upstream repositories for updates from the last 30 days and generate a sync analysis report.

Frequently Asked Questions about ce:sync-upstream

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

FAQPage Schema
How do I check for upstream repository updates in a git fork?▼

Run the sync-upstream command, which fetches upstream changes via git fetch and the GitHub API, covering the last 30 days of commits and releases. It produces a structured Markdown report summarizing relevant updates for your review.

How to filter noise commits when reviewing upstream changes?▼

The command automatically excludes chore commits, dependency bumps, dependabot activity, and merge commits from analysis. Remaining changes are rated high, medium, or low relevance with a stated reason for each rating.

What tools are required to detect upstream repository updates?▼

You need the GitHub CLI (gh) authenticated via gh auth status, and a git remote named upstream pointing to the source repository. Missing prerequisites mark the affected repository as failed without stopping the overall scan.

Can I track multiple upstream repositories at once?▼

Yes, repositories are configured in docs/sync-reports/upstream-repos.json with per-repo strategies: git-native, github-api, or releases. If the config file is missing, a default four-repository configuration is created automatically.

What happens after the upstream sync report is generated?▼

The report is saved to docs/sync-reports/ with a date-stamped filename, and you are prompted to choose a next step: discuss high-relevance items, create an integration plan, execute a squash merge from upstream, or defer.