verified-merge

Merges GitHub pull requests while preserving users' verified commit signatures.

6|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/kubuszok/sge --skill verified-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verified-merge
Source: https://github.com/kubuszok/sge/tree/main/.claude/skills/verified-merge
Command: npx skills add https://github.com/kubuszok/sge --skill verified-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that your verified commits are preserved in GitHub's history when merging pull requests, avoiding the loss of your signature and preventing the "merge-locally-then-push" issue.

Core Features & Use Cases

  • Verified Commit Preservation: Merges pull requests while keeping your verified commits signed.
  • Avoids Re-signing: Works around GitHub's rebase-merge re-signing every commit.
  • Merge Locally-Then-Push Issue: Solves the problem of "merge-locally-then-push" not marking the PR as merged.
  • Bot PRs: Skips bot pull requests, preserving verification for your work only.

Quick Start

To merge a pull request while preserving your verified commits, use the command: /verified-merge <pr-number|branch>

Frequently Asked Questions about verified-merge

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

FAQPage Schema
How do I merge a pull request while keeping my verified commit signature intact?

To preserve your verified commit signature when merging a pull request, this Skill merges the PR on GitHub while keeping your commits signed in the repository history. It automatically skips bot pull requests to ensure only your verified work is maintained.

Why does GitHub rebase-merge re-sign my commits and how can I avoid it?

GitHub's rebase-merge re-signs every commit, altering your original signature. This Skill works around that rebase-merge re-signing issue by handling the merge process, ensuring your original verified commits are preserved when merging pull requests on GitHub.

Do I need Git and GitHub CLI configured to preserve commit verification when merging?

Yes, you need Git and GitHub CLI installed with commit signing configured to preserve commit verification when merging. These prerequisites allow the Skill to properly handle the merge process and maintain your verified commit signatures in the repository history.

What's the best way to fix the merge locally then push issue not marking a PR as merged?

The best way to fix the merge-locally-then-push issue is using this Skill, which solves the problem of local merges not marking the PR as merged on GitHub. It ensures the pull request status updates correctly while preserving your verified commits in the history.

Can I skip bot pull requests when merging to preserve my own commit verification?

Yes, you can skip bot pull requests when merging to preserve your own commit verification. This Skill automatically skips bot PRs, ensuring that only your work retains its verified commit signatures in the GitHub history during the pull request merge process.