squash-merge

Validate and squash-merge pull requests into main branches with GitHub CLI.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/OGismatulin/zeroclaw-source --skill squash-merge-ogismatulin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: squash-merge
Source: https://github.com/OGismatulin/zeroclaw-source/tree/main/.claude/skills/squash-merge
Command: npx skills add https://github.com/OGismatulin/zeroclaw-source --skill squash-merge-ogismatulin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of squash-merging pull requests into the main branch, ensuring a clean commit history and proper linking of PRs and issues.

Core Features & Use Cases

  • Automated PR Validation: Checks PR status, target branch, merge conflicts, and review approvals before merging.
  • Context-Aware Merging: Fetches commit details and formats squash messages according to conventional standards.
  • Use Case: When managing multiple feature branches, developers can use this Skill to perform consistent, compliant merges without manual effort.

Quick Start

Ask the AI to squash-merge PR #123 into the main branch.

Frequently Asked Questions about squash-merge

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

FAQPage Schema
How do I automate a squash merge for a pull request into the main branch?

Automating a squash merge integrates pull requests into the main branch by validating PR status, formatting commit messages, and executing the merge with proper attribution. This ensures clean, traceable history and compliance with development standards.

What is checked before a pull request is squash-merged automatically?

Before a pull request is squash-merged, automated validation checks the PR status, target branch, merge conflicts, and review approvals. This prevents broken or unreviewed code from entering the main branch.

Do I need GitHub CLI to automate squash merging pull requests?

Yes, you need GitHub CLI and correct permissions to merge pull requests. These dependencies allow the automated process to fetch commit details and execute squash merges with proper attribution.

How are commit messages formatted during an automated squash merge?

During an automated squash merge, commit messages are fetched and formatted according to conventional standards. This context-aware merging ensures proper linking of pull requests and issues in the repository history.

When should I use an automated squash merge for repository management?

Use an automated squash merge for repository management workflows requiring clean, traceable history and compliance with development standards. It is ideal when managing multiple feature branches and needing consistent, compliant merges without manual effort.