skills.rest
tae0y
tae0yCOMMUNITY
Explore all skills by this author →
GitHub

template-downstream

Apply upstream template changes while preserving customized local files.

14|Updated Feb 15, 2026
Search Tags:#automation#template#tooling#diff#sync#project-management#upstream
One-click install
npx skills add https://github.com/tae0y/python-project-template --skill template-downstream
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: template-downstream
Source: https://github.com/tae0y/python-project-template/tree/main/.claude/skills/template-downstream
Command: npx skills add https://github.com/tae0y/python-project-template --skill template-downstream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update the current project by pulling applicable changes from the upstream python-project-template repository into the local project. Only files that exist upstream are updated, and project-specific customizations are preserved; files that no longer exist upstream are not deleted.

Core Features & Use Cases

  • Diff-aware updates: apply only files that exist upstream and differ, preserving project-only files.
  • Safe, non-destructive syncing: avoid deleting local files and report conflicts for manual review.
  • Scoped resolution: determine TEMPLATE_ROOT via user path, same remote, or shallow clone to minimize network usage.

Quick Start

Run the downstream sync to apply upstream template updates to your project while preserving customizations.

Frequently Asked Questions about template-downstream

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

FAQPage Schema
How do I sync upstream template changes without overwriting customized files?▼

Diff-aware syncing applies upstream template changes to your local project without overwriting customized files. It updates only files that exist upstream and differ, while preserving project-specific files and reporting conflicts for manual review.

What happens to local files that no longer exist in the upstream template?▼

When syncing upstream templates, local files that no longer exist upstream are not deleted. The operation is non-destructive and preserves project-only files to prevent data loss during template updates.

How does the tool determine the upstream source for template syncing?▼

Upstream source resolution determines the template root via user-provided paths, the same remote origin, or a shallow clone. This scoped resolution minimizes network usage while locating the correct upstream template source.

Does syncing upstream templates require explicit confirmation before applying updates?▼

Yes, safe operations require explicit confirmation for significant updates. The sync enforces safety by keeping local settings and localdocs intact, ensuring you review and approve major template changes before they are applied.

Can I sync an upstream template using a shallow clone to minimize network usage?▼

Yes, scoped resolution supports shallow clones to minimize network usage when determining the upstream source. This allows you to fetch template updates efficiently without downloading the entire repository history.

Related Skills

Explore More Software Engineering Skills→
idvorkinidvorkin
1

up-to-date

Sync local git repositories with upstream or origin main branches.

Community
Advanced
yellow-seedyellow-seed

template-sync

Synchronize template updates from yellow-seed/template while preserving local customizations.

Community
Advanced
richardmbaileyrichardmbailey

rb-setup-local-agent-skills

Audit local RB agent skill installations and symlink targets across Codex and Claude Code.

Community
Intermediate
tranhieutttranhieutt
70

sync-template

Synchronize the .claude directory from an upstream template repository.

Community
Intermediate