skills.rest
coopeverything
coopeverythingCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sync-to-main

Sync production-validated code from yolo to main with CI reconciliation.

Updated Aug 27, 2026
Search Tags:#automation#git#branch#reconciliation#CI#sync-to-main
One-click install
npx skills add https://github.com/coopeverything/TogetherOS --skill sync-to-main
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-to-main
Source: https://github.com/coopeverything/TogetherOS/tree/main/.claude/skills/sync-to-main
Command: npx skills add https://github.com/coopeverything/TogetherOS --skill sync-to-main

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains main CI-compliant branch by selectively syncing production-validated code from yolo with two-phase gating.

Core Features & Use Cases

  • Phase 1 automatic: Creates WIP markers in main at 5% milestones
  • Phase 2 user-initiated: Syncs code after production validation with CI reconciliation
  • Reconciles yolo's code to meet main CI requirements (lint, build, validation)
  • Keeps status synchronization (STATUS_v2.md, progress-log.md)

Quick Start

  • Say "sync [module] to main" to create a WIP marker in main at the milestone.
  • After production validation, say "approve main sync" or "reconcile [module] with main" to perform Phase 2.

Frequently Asked Questions about sync-to-main

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

FAQPage Schema
How do I automatically sync code from a relaxed CI branch to a strict main branch?▼

Sync-to-main coordinates code synchronization from yolo to main after production validation using a two-phase workflow: Phase 1 automatically creates WIP markers at 5% milestones, and Phase 2 performs manual sync with cherry-pick and CI reconciliations to ensure main CI compliance.

Can I selectively cherry-pick commits when syncing to main?▼

Yes. Sync-to-main enables selective commit cherry-picking during Phase 2, allowing you to choose specific commits from yolo to merge into main while reconciling lint, build, and validation requirements.

What happens if there are merge conflicts when syncing branches?▼

Sync-to-main prompts you to resolve conflicts during the sync process and automatically applies fixes for lint and build issues to ensure the merged code meets main CI requirements before completion.

How does sync-to-main keep progress tracked across branches?▼

Sync-to-main maintains status synchronization by updating STATUS_v2.md and progress-log.md files during both WIP marker creation and code sync phases, keeping your workflow state consistent across yolo and main.

Do I need to manually create pull requests when syncing to main?▼

No. Sync-to-main generates PR steps automatically as part of Phase 2, handling the PR creation workflow so you can approve and merge validated code without manual intervention.

What CI requirements does sync-to-main reconcile between branches?▼

Sync-to-main reconciles yolo code to meet main CI standards by auto-fixing lint errors, resolving build failures, and running validation checks, ensuring all synced commits pass strict main CI gates.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

diff-analyze

Analyze git differences and commit history between the current branch and origin main.

Community
Basic
ITSaltITSalt
23

nacl-tl-release

Automate end-to-end software releases by merging PRs, validating CI, and publishing changelogs.

Community
Advanced
pegasus-isipegasus-isi

babysit-pr

Automate pull request lifecycle with GitHub CLI and git worktrees.

Official
Advanced
heyAyushhheyAyushh
3

commit-push

Stage all changes, commit with conventional prefixes, and push to the current branch.

Community
Basic