skills.rest
Obsidian-Owl
Obsidian-OwlOFFICIAL
Explore all skills by this author →
WebsiteGitHub

speckit-merge-check

Detect contract changes, merge conflicts, and architecture compliance issues on Epic branches.

4|11|Updated Dec 14, 2025
Search Tags:#merge-conflicts#contract-tests#pre-pr#architecture-compliance#merge-check#epic-branch#contract-change
One-click install
npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-merge-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-merge-check
Source: https://github.com/Obsidian-Owl/floe/tree/main/.claude/skills/speckit-merge-check
Command: npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-merge-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate Epic branches before PR by detecting contract changes, merge conflicts, and architecture issues that could block merges.

Core Features & Use Cases

  • Contract-change detection and classification (Safe, Caution, Breaking)
  • Merge-conflict simulation against main to surface conflicts
  • Pre-PR contract tests and type-check validations
  • Architecture compliance checks for import boundaries
  • Use Case: Before opening a PR for epic-123, run this to ensure no breaking changes or conflicts exist.

Quick Start

Run speckit-merge-check on the current Epic branch to begin pre-PR validation.

Frequently Asked Questions about speckit-merge-check

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

FAQPage Schema
How do I check an epic branch for merge conflicts before opening a PR?▼

To check an epic branch for merge conflicts before a PR, run a pre-PR validation that simulates a rebase against main. This surfaces potential conflicts early by scoping the current branch against the target branch in multi-package environments.

What is contract-change detection and how does it classify breaking changes?▼

Contract-change detection identifies modifications in cross-team APIs and classifies them as Safe, Caution, or Breaking. This classification happens during pre-PR validation to enforce contract stability and prevent blocking merges in multi-package environments.

How do I validate architecture compliance and import boundaries in a multi-package environment?▼

You validate architecture compliance by enforcing import-boundary validations during your pre-PR checks. This ensures that cross-team changes within multi-package environments respect the defined structural architecture before merging into main.

Can I run contract tests and type-check validations on an epic branch before merging to main?▼

Yes, you can run contract tests and type-check validations on an epic branch before merging to main. This validates that no breaking changes exist and ensures the epic branch is fully PR-ready for integration.

Related Skills

Explore More Software Engineering Skills→
linkerdoglinkerdog
15

rara-docs-spec

Maintain stable RARA feature specifications under docs/features/ with validation matrices.

Official
Basic
ajsai47ajsai47
11

land-and-deploy

Merge GitHub pull requests and verify production health after deployment.

Community
Advanced
mvillmowmvillmow
18

quality-run-linters

Run configured linters including mojo-format, markdownlint, and pre-commit checks in check or fix mode.

Community
Intermediate
ousiassousiass

resolve-conflicts-en

Resolve GitHub pull request merge conflicts using an isolated Git worktree.

Community
Advanced