skills.rest
kelsi-andrewss
kelsi-andrewssCOMMUNITY
Explore all skills by this author →
GitHub

merge

Validate branch merges with build, test, lint, and review gates.

Updated Apr 8, 2026
Search Tags:#automation#git#code review#merge#spec#regression testing#branch strategy
One-click install
npx skills add https://github.com/kelsi-andrewss/capstone-toolkit --skill merge-kelsi-andrewss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/kelsi-andrewss/capstone-toolkit/tree/main/skills/merge
Command: npx skills add https://github.com/kelsi-andrewss/capstone-toolkit --skill merge-kelsi-andrewss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature work too often lands in shared branches without spec verification, automated build/test/lint gates, or regression reviews, which leads to regressions, unreviewed diffs, and branching chaos; this merge skill enforces the workflow before code is allowed to land.

Core Features & Use Cases

  • Branch discipline: Detects the current branch, validates naming conventions, and enforces the feature→dev→main flow so you never merge a feature directly into main.
  • Gate orchestration: Runs build, test, and lint pipelines, analyzes the diff, and walks acceptance criteria against the spec before merging to keep quality high.
  • Review & regression safeguarding: Launches a reviewer agent, blocks on blocking findings, and re-runs tests post-merge to catch regressions introduced by the merge itself.

Quick Start

Invoke /merge with your chosen branch and flags so the tool enforces branch strategy, spec checks, build/test/lint, reviewer, and regression gates before merging.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I enforce spec verification before merging a feature branch into dev or main?▼

To enforce spec verification before merging, this Skill discovers your project spec, runs build/test/lint pipelines, and walks acceptance criteria against the spec to ensure unverified changes never enter shared branches.

What's the best way to automate git branch strategy and prevent direct merges to main?▼

Automating git branch strategy is achieved by validating branch naming and enforcing the feature→dev→main workflow, blocking any direct feature-to-main merges before code is allowed to land.

How do I run regression testing automatically after a git merge?▼

Regression testing runs automatically post-merge by re-executing your test suite to catch any regressions introduced by the merge itself before declaring success.

Can I do a dry-run merge to analyze diffs and check acceptance criteria without committing?▼

Yes, you can use the dry-run flag to analyze diffs and verify acceptance criteria against the spec without executing the actual merge or committing changes.

How does automated code review work for blocking unreviewed git diffs?▼

Automated code review launches a reviewer agent to analyze the diff, blocks the merge on blocking findings, and screens all changes before allowing the merge to proceed.

Do I need a specific branch workflow to use spec-driven merge validation?▼

Spec-driven merge validation targets Claude Code projects following a feature→dev→main branch workflow, requiring spec discovery and acceptance criteria verification before any merge executes.

Related Skills

Explore More Software Engineering Skills→
quaid-appquaid-app
3

git-workflow

Enforce a dev-first three-branch model with issue-based workflows and PR merges.

Official
Intermediate
tamnguyentommy-rgbtamnguyentommy-rgb
2

post_merge_setup

Automate post-merge script execution and workflow reconciliation in CI pipelines.

Community
Advanced
tachfineamnaytachfineamnay

Git Workflow & CI/CD

Standardize Git workflows and CI/CD pipelines with Husky and GitHub Actions.

Community
Intermediate
cosmixcosmix
53

ci-cd

Design and automate CI/CD pipelines for GitHub Actions, GitLab CI, and Jenkins.

Community
Advanced