skills.rest
SiTaggart
SiTaggartCOMMUNITY
Explore all skills by this author →
Website𝕏@SiTaggartGitHub

sync-upstream

Map upstream paths to local equivalents and generate a sync report.

2|Updated Feb 9, 2026
Search Tags:#reports#agents#sync#mapping#upstream#path-flattening
One-click install
npx skills add https://github.com/SiTaggart/.agents --skill sync-upstream
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-upstream
Source: https://github.com/SiTaggart/.agents/tree/main/.claude/skills/sync-upstream
Command: npx skills add https://github.com/SiTaggart/.agents --skill sync-upstream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Categorize upstream changes by mapping upstream paths to local equivalents.

Core Features & Use Cases

  • Path mapping across upstream and local structures to normalize agent, command, and skill locations.
  • Flatten hierarchical upstream layouts into a flat local directory for governance and review.
  • Adaptation-ready with documented notes for integrating upstream changes into the local repository.

Quick Start

Map the upstream changes to the local .agents structure and review the resulting alignment report.

Frequently Asked Questions about sync-upstream

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

FAQPage Schema
How do I map upstream paths to local equivalents when syncing agents and skills?▼

Mapping upstream paths to local equivalents categorizes upstream changes by applying longest-prefix path mappings, flattening hierarchical upstream layouts into a flat local directory structure for governance and review.

What is the best way to flatten hierarchical upstream directory structures into a local repository?▼

Flattening upstream directory structures normalizes agent, command, and skill locations into a flat local directory, enforcing longest-prefix path mappings and generating a structured sync report detailing updates and actions.

How does skip-pattern handling work during upstream-to-local sync workflows?▼

Skip-pattern handling during upstream-to-local sync workflows filters specific upstream paths, ensuring only relevant agents, commands, and skills are mapped to local equivalents while excluded paths are omitted from the structured sync report.

Can I generate a structured sync report for upstream changes integrated from the compound-engineering-plugin?▼

Generating a structured sync report for the compound-engineering-plugin categorizes upstream changes, maps paths to local equivalents, and details updates and actions required for integrating into the local repository.

Do I need longest-prefix path mappings to align upstream agents with a local directory?▼

Longest-prefix path mappings are required to align upstream agents with a local directory, ensuring accurate normalization of agent, command, and skill locations during the upstream-to-local sync workflow.

Why does path flattening fail to match upstream skill locations to my local repository structure?▼

Path flattening may fail to match upstream skill locations if longest-prefix path mappings are not correctly configured, preventing proper normalization of hierarchical upstream layouts into the flat local directory structure.

Related Skills

Explore More Software Engineering Skills→
grahama1970grahama1970
1

skills-sync

Sync local skills with an upstream agent-skills repository via rsync.

Community
Advanced
gileckgileck

full-project-audit

Audit repository deviations from guidelines and architecture rules without code changes.

Community
Advanced
gmelligmelli
1

aget-propose-skill

Create structured Markdown skill proposals with validation and governance checks.

Community
Intermediate
caio-moliveiracaio-moliveira
36

deep-agents-memory

Configure pluggable backends for ephemeral and persistent agent storage.

Community
Advanced