neb-update-platform

Synchronize local NebInfra skills with upstream platform changes and generate PRs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-update-platform
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neb-update-platform
Source: https://github.com/nebinfra/nebcore-ai-skills/tree/main/neb-update-platform
Command: npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-update-platform

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronizes the upstream platform repository with NebInfra's local copy, preserving amendments and validating SDK compatibility, then automating PR creation for review.

Core Features & Use Cases

  • Upstream synchronization: fetches changes, diffs content, and applies updates to local skills while preserving NebInfra amendments.
  • Amendment preservation and validation: retains NebInfra-specific blocks and ensures references remain valid.
  • Quality gate and PR automation: checks for breaking changes, validates compatibility, and opens a PR for human review.

Quick Start

Run the update-platform workflow to fetch upstream changes, apply nebinfra amendments, validate SDK compatibility, and create a PR for review.

Frequently Asked Questions about neb-update-platform

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

FAQPage Schema
How do I sync local skill copies with upstream platform changes?

To sync local skill copies with upstream platform changes, this Skill fetches upstream repository updates, diffs content, and applies changes to local folders while preserving custom amendments. It automates the synchronization process and validates SDK compatibility before generating a pull request for review.

How does amendment preservation work when applying upstream updates?

Amendment preservation works by retaining your specific custom blocks during the upstream synchronization process. The Skill diffs the fetched upstream changes against your local copy, applies platform updates, and ensures your custom amendments and references remain valid and intact.

Do I need a clean working directory to automate pull request generation?

Yes, you need a clean working directory to automate pull request generation. The Skill also requires Git to manage diffs and pull requests, and access to ~/oss/paperclip with its origin pointing to the correct upstream repository to properly fetch and apply updates.

What is the best way to automate SDK compatibility checks for platform updates?

The best way to automate SDK compatibility checks is to run the update-platform workflow. It functions as a quality gate during synchronization, automatically validating references and checking for breaking changes before opening a PR for human review across multiple folders.

Why does the upstream sync fail when my local repository has uncommitted changes?

Upstream sync fails with uncommitted changes because the workflow requires a clean working directory to safely manage diffs and preserve amendments. You must commit or stash local modifications before running the platform update to prevent Git conflicts during the automated pull request generation.