synthesis-code-integration

Coordinate multi-contributor integration for synthesis-coded projects using adopt-and-adapt governance.

15|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/synthesisengineering/synthesis-skills --skill synthesis-code-integration-synthesisengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: synthesis-code-integration
Source: https://github.com/synthesisengineering/synthesis-skills/tree/main/synthesis-code-integration
Command: npx skills add https://github.com/synthesisengineering/synthesis-skills --skill synthesis-code-integration-synthesisengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When multiple contributors work on synthesis-coded projects, direct merges can cause regressions and architectural drift. This skill defines adopt-and-adapt integration to preserve intent while enabling gradual improvements.

Core Features & Use Cases

  • Provides a structured workflow for selective integration: adopt the design, adapt the implementation, and verify quality gates.
  • Defines roles (Lead Synthesist vs Contributors) and responsibilities to maintain architectural integrity.
  • Guides integration of external contributions with fresh main-based integration branches, feedback cycles, and squash-free attribution.

Quick Start

Begin by establishing a fresh integration branch from main, read the contributor's changes, and selectively apply them using adopt-and-adapt rules.

Frequently Asked Questions about synthesis-code-integration

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

FAQPage Schema
How do I integrate external contributor code without causing regressions?

To integrate external contributor code without regressions, use an adopt-and-adapt workflow on a fresh main-based branch to selectively apply changes, enforce quality gates, and verify alignment with the current main branch.

What is the adopt-and-adapt strategy for multi-contributor codebases?

Adopt-and-adapt integration means adopting the contributor's design intent while adapting the implementation to fit the current architecture, preventing architectural drift during multi-contributor integration.

How do I maintain correct attribution when selectively integrating code changes?

You maintain correct attribution during selective integration by using squash-free integration branches, ensuring external contributors receive proper credit while the Lead Synthesist guides incremental adaptations.

What is the best way to manage branch hygiene for collaborative coding projects?

The best way to manage branch hygiene for collaborative coding is to establish fresh integration branches from main, enforce structured review workflows, and apply rigorous quality gates to prevent regressions.

Can I use this integration workflow for projects with rapidly evolving main branches?

Yes, this integration workflow is designed for codebases with evolving main branches, using incremental integration and feedback cycles to keep external contributions aligned with the latest main branch state.