upstream-sync

Detect upstream specification and documentation changes affecting enterprise skills.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/justSteve/GasTownOperations --skill upstream-sync-juststeve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upstream-sync
Source: https://github.com/justSteve/GasTownOperations/tree/main/.claude/skills/upstream-sync
Command: npx skills add https://github.com/justSteve/GasTownOperations --skill upstream-sync-juststeve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects and summarizes changes in upstream specifications, example repositories, and documentation so teams can quickly find and address spec drift that would affect enterprise skill behavior and documentation.

Core Features & Use Cases

  • Source monitoring: Checks agentskills/agentskills commits, anthropics/skills commits, Claude Code documentation pages, and a skills-ref library version for changes since the last sync.
  • Delta summarization: Produces one-line commit summaries, documents new or deprecated frontmatter fields, and highlights items that require updates to enterprise SKILL.md files or terminology mappings.
  • Impact assessment & update: Provides a checklist-driven impact assessment and can update enterprise docs and the stored sync state to record last_synced and change notes.
  • Use case: Run daily to catch breaking changes to skill resolution semantics or when investigating a reported behavioral regression after an upstream change.

Quick Start

Run upstream-sync to compare upstream repos and docs against references/sync-state.json and generate an impact report for review.

Frequently Asked Questions about upstream-sync

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

FAQPage Schema
How do I detect upstream changes in GitHub specification repositories that affect my enterprise skills?

To detect upstream changes in GitHub specification repositories, you can monitor commits against a stored sync-state JSON to produce delta summaries and impact assessments for enterprise skills. This requires GitHub API access to compare recent repository commits.

What is spec drift monitoring for Claude Code documentation and Agent Skills?

Spec drift monitoring for Claude Code documentation tracks upstream changes in example repos and docs to identify breaking updates. It documents new or deprecated frontmatter fields and highlights items requiring updates to enterprise SKILL.md files.

How do I generate an impact assessment for breaking changes in upstream skill resolution semantics?

You can generate an impact assessment for breaking changes by comparing upstream documentation commits against a sync-state JSON file. This produces a checklist-driven report summarizing necessary updates to terminology mappings and enterprise skill behavior.

Do I need GitHub API access to monitor upstream specification changes and update sync state?

Yes, you need GitHub API access and web fetch capabilities to monitor upstream specification changes. The process checks repository commits and documentation pages, then updates a stored references/sync-state.json file to record the last_synced timestamps and change notes.

When should I run an upstream sync investigation for enterprise documentation?

You should run an upstream sync investigation daily to catch breaking changes proactively, or immediately when investigating a reported behavioral regression caused by an upstream change in Anthropic example repos or Claude Code documentation.

What's the best way to keep enterprise specs aligned with Anthropic example repos and skills-ref dependencies?

The best way to keep enterprise specs aligned is to perform daily delta comparisons using a sync-state JSON file. This monitors agentskills commits, Anthropic example repos, and skills-ref dependency metadata to generate commit summaries and update enterprise docs.