kspec-merge

Merge approved Git task branches into integration branches with kspec review gates.

1|2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/lepahc/kynetic-spec --skill kspec-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kspec-merge
Source: https://github.com/lepahc/kynetic-spec/tree/main/.agents/skills/kspec-merge
Command: npx skills add https://github.com/lepahc/kynetic-spec --skill kspec-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge approved work into an integration branch. Local-first git merge with gates based on kspec review disposition — approved status, passing checks, and resolved blocker threads.

Core Features & Use Cases

  • Gate checks: review disposition must be "approved", required checks must pass, and there must be no unresolved blocker threads.
  • Integration-branch targeting: supports dispatch-provided targets or manual branches for integration.
  • Merge lifecycle: verify state, perform merge, handle conflicts, close the review, and clean up branches.

Quick Start

Run the kspec-merge flow to merge an approved task branch into the designated integration branch.

Frequently Asked Questions about kspec-merge

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

FAQPage Schema
How do I merge a git branch only after review approval and passing checks?

Guarded merges integrate approved work by enforcing gates: review disposition must be approved, required checks must pass, and all blocker threads must be resolved before merging a task branch.

What is the best way to handle merge conflicts during local-first git integration?

During a local-first merge, the flow coordinates conflict handling as part of the merge lifecycle, pausing integration to resolve conflicts before proceeding to close the review and clean up branches.

Can I manually target a specific integration branch instead of using a dispatched target?

Yes, integration-branch targeting supports both dispatch-provided targets and manually specified branches, allowing you to direct the approved task branch merge into the correct integration stream.

Does the merge flow handle branch cleanup after integrating approved work?

Yes, post-merge cleanup is a core step in the merge lifecycle, automatically handling branch cleanup and closing the review after the approved work is successfully integrated into the target branch.

Why would a guarded merge fail to start if I have unresolved blocker threads?

A guarded merge requires resolved blocker threads as a gate; any unresolved blockers will prevent the merge lifecycle from starting, ensuring only fully vetted and approved work is integrated.

When do I need a local-first merge workflow with review gates?

You need a local-first merge workflow when integrating approved work into a Git-based project that requires strict kspec review gates, passing checks, and resolved blockers before merging task branches.