sync-main-into-vipps

Review main branch commits absent from vipps and generate adoption recommendations.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/eivindeb/agent-skills --skill sync-main-into-vipps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-main-into-vipps
Source: https://github.com/eivindeb/agent-skills/tree/main/.cursor/skills/sync-main-into-vipps
Command: npx skills add https://github.com/eivindeb/agent-skills --skill sync-main-into-vipps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps manage the complex process of integrating changes from a main development branch into a feature-specific branch (vipps), ensuring that valuable generic improvements are adopted while respecting branch-specific constraints.

Core Features & Use Cases

  • Commit Review: Analyzes commits present in main but missing in vipps.
  • Decision Making: Provides clear recommendations (adopt, partial adopt, skip, supersede) for each commit based on defined constraints.
  • Integration Planning: Generates an actionable plan for integrating selected commits, including cherry-picking and manual porting guidance.
  • Use Case: When a new set of general performance improvements are merged into main, this skill helps you decide which of those improvements should be brought into the vipps branch, considering its unique workflow requirements.

Quick Start

Review commits present on main but missing from vipps, evaluate value under vipps constraints, and produce commit-by-commit adopt/partial/skip recommendations.

Frequently Asked Questions about sync-main-into-vipps

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

FAQPage Schema
How do I analyze missing git commits between a main branch and a feature branch?

To analyze missing git commits between branches, review the commit logs absent from the target branch and categorize each commit for adoption based on predefined workflow constraints. This generates a commit-by-commit analysis with clear recommendations for integration.

How do I decide which commits to cherry-pick from main into a constrained feature branch?

To decide which commits to cherry-pick, evaluate each commit's value under the target branch's specific constraints and generate adopt, partial adopt, skip, or supersede recommendations. This provides an actionable integration plan for selectively porting changes.

What is the best way to plan a branch integration workflow for diverged git repositories?

The best way to plan branch integration is to generate a commit-by-commit analysis that produces an actionable integration plan, including cherry-picking and manual porting guidance. This ensures valuable generic improvements are adopted while respecting branch-specific constraints.

Does this branch synchronization workflow require local git clones and remote authentication?

Yes, this branch synchronization workflow requires local git clones and delegated remote authentication to function properly. It relies on standard git commands like git log and git show to review and categorize missing commits.

Can I automate code review for branch-specific commit adoption decisions?

You can automate code review for commit adoption by analyzing commits present in the main branch but missing in the target branch. The system automatically categorizes each commit and updates a decision log with integration recommendations.

What are the limitations of automating commit integration from main into a custom branch?

Limitations of automating commit integration include the necessity of local clones, delegated remote authentication, and adherence to specific workflow constraints. Complex commits may require manual porting guidance rather than direct cherry-picking.