skills.rest
ResearchMonkey
ResearchMonkeyCOMMUNITY
Explore all skills by this author →
GitHub

foundation-sync

Bidirectionally synchronize a fork with Foundation_template using git subtree.

Updated Apr 6, 2026
Search Tags:#automation#workflow#sync#code-review#fork-management#git-subtree#foundation-template
One-click install
npx skills add https://github.com/ResearchMonkey/Foundation_template --skill foundation-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: foundation-sync
Source: https://github.com/ResearchMonkey/Foundation_template/tree/main/.claude/skills/foundation-sync
Command: npx skills add https://github.com/ResearchMonkey/Foundation_template --skill foundation-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a forked project and Foundation_template in sync using git subtree, reducing drift and manual merge work between upstream and forked workstreams.

Core Features & Use Cases

  • Bidirectional synchronization between Foundation_template and a fork via git subtree.
  • Maintains fork-specific customizations while incorporating upstream updates.
  • Useful for maintainers who need to push changes back for review.

Quick Start

Run foundation-sync init on your local-project-path to set up the subtree, then run foundation-sync pull or foundation-sync push to keep both sides aligned.

Frequently Asked Questions about foundation-sync

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

FAQPage Schema
How do I sync a fork with an upstream template using git subtree?▼

Git subtree sync keeps forked projects aligned with a canonical Foundation_template by merging upstream changes and pushing contributions back. It uses git subtree operations to preserve fork-specific customizations across both directions.

What is bidirectional git subtree synchronization for fork management?▼

Bidirectional git subtree sync merges upstream template updates into a fork while pushing customizations back for review. It maintains separate workstreams while reducing manual merge work and drift between both directions.

How do I keep fork-specific customizations while pulling upstream template updates?▼

To keep fork-specific customizations while pulling upstream template updates, run foundation-sync pull on your local project path. This merges upstream changes via git subtree without overwriting your local modifications.

Can I push fork changes back to the Foundation_template for code review?▼

Yes, you can push fork changes back to the Foundation_template for code review. The system enforces review on pushed changes, allowing maintainers to submit contributions upstream while keeping the fork synced.

Does git subtree sync work without modifying the .foundation subtree prefix?▼

Git subtree sync requires the .foundation subtree prefix to correctly identify and manage the template paths. It enforces review on pushed changes and uses this prefix to perform bidirectional merges between the fork and Foundation_template.

What are the limitations of using git subtree for fork and template synchronization?▼

Using git subtree for fork and template synchronization requires understanding subtree operations and the .foundation prefix. It is limited to workflows where forks need to stay aligned with canonical templates while preserving customizations, and it enforces review on pushed changes.

Related Skills

Explore More Software Engineering Skills→
chiubakachiubaka
1

org-subtree-status

Compare embedded org subtree prefix with upstream org repository status.

Community
Intermediate
kage1020kage1020

check-pr-comments

Apply pull request comment feedback as code changes and verify tests.

Community
Intermediate
MomoDavilukeMomoDaviluke
2

requesting-code-review

Automate structured code reviews before merging branches using templates and SHA inputs.

Community
Intermediate
rahulrajaramrahulrajaram

git-status-report

Report Git repository and submodule synchronization status against remote tracking branches.

Community
Intermediate