skills.rest
missingbulb
missingbulbCOMMUNITY
Explore all skills by this author →
GitHub

merge-to-main

Merges the current branch or pull request into main using squash merge via GitHub.

Updated Jun 12, 2026
Search Tags:#git#pull request#github#merge#main branch#squash merge#ci checks
One-click install
npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill merge-to-main-missingbulb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-to-main
Source: https://github.com/missingbulb/GoogleCalendarEventCreator/tree/main/.claudinite/shared/packs/git-github/skills/merge-to-main
Command: npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill merge-to-main-missingbulb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the manual, error-prone steps of landing an approved change: creating a PR if none exists, waiting for CI checks, squash-merging with the right title, syncing local main, and capturing the session log. ## Core Features & Use Cases - End-to-end merge workflow: Creates a pull request when none exists, waits for check runs to pass, then squash-merges with a standardized title. - Issue auto-closing: Adds Closes #<issue> to the PR body so the linked issue closes on merge. - Post-merge automation: Syncs local main, captures the conversation log, and triggers a production verification check. - Use Case: After a reviewer replies "LGTM" on your branch, invoke this Skill to land the change on main without touching the GitHub UI. ## Quick Start Say "LGTM, merge this branch into main" and the Skill will create or find the PR, wait for checks, squash-merge, and sync your local main.

Frequently Asked Questions about merge-to-main

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

FAQPage Schema
How do I merge a pull request into main from the command line or AI assistant?▼

Invoke the merge-to-main flow after approval: it loads the GitHub create_pull_request and merge_pull_request tools, waits for any check runs to pass, then performs a squash merge with the title formatted as subject plus PR number.

How to squash merge a GitHub PR automatically after LGTM?▼

The Skill triggers on an LGTM approval, creates a PR if none exists for the branch, waits for CI checks, and calls merge_pull_request with merge_method set to squash. It then syncs local main with git checkout and pull.

Does the merge wait for CI checks to pass?▼

Yes. If the pull request has check runs, the workflow waits for them to pass before merging. If there are no check runs configured, it merges immediately without waiting.

Can a project override the default merge method or CI gating?▼

Yes. If the project's CLAUDE.md names a merge-policy file, that file overrides the divergent points such as merge method and CI gating. The Skill does not search for a policy file that is not explicitly named.

What happens after the squash merge completes?▼

Local main is synced via git checkout main and git pull, the conversation log is captured with the capture-log script when the repo declares claudinite-growth, and a production verification check runs to decide if a follow-up issue is needed.

Related Skills

Explore More Software Engineering Skills→
PacificStudioPacificStudio
264

land

Enforce CI and branch-state checks before merging Git changes.

Official
Intermediate
Fu-JieFu-Jie
286

release-finalizer

Merge release PRs into main and close linked issues automatically.

Community
Advanced
NJX-njxNJX-njx
55

prepare-pr

Rebase GitHub pull requests onto main, fix review issues, and run build and test gates.

Community
Intermediate
mjbellantonimjbellantoni

squash-merge

Draft standardized commit messages and squash merge GitHub pull requests via gh CLI.

Community
Intermediate