github-mr

Creates GitHub pull requests merging the current branch into develop and cleans up worktrees.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill github-mr-marcocpt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-mr
Source: https://github.com/marcocpt/trae_skills/tree/main/github-mr
Command: npx skills add https://github.com/marcocpt/trae_skills --skill github-mr-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually creating pull requests, writing change summaries, linking issues, and cleaning up branches after merging is repetitive and error-prone. This Skill automates the entire merge workflow on GitHub so developers can finish a feature branch with a single instruction. ## Core Features & Use Cases - Automated Pull Request Creation: Creates a PR from the current branch into the develop branch with a comment describing what changed, how it was verified, and which Issue it relates to. - Post-Merge Cleanup: Deletes the current branch and its git worktree after a successful merge. - Issue Management: Writes discussion details, design decisions, and background context into GitHub Issue comments and closes the Issue. - Use Case: After finishing a feature in a git worktree, ask the assistant to merge it—the PR is created with full context, the Issue is documented and closed, and the local branch and worktree are removed. ## Quick Start Merge my current branch into develop on GitHub, document the changes and related Issue in the PR comment, then clean up the branch and worktree.

Frequently Asked Questions about github-mr

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

FAQPage Schema
How do I create a GitHub pull request from the command line?

Use the GitHub CLI with 'gh pr create' specifying the base branch such as develop and a body describing the changes. This Skill automates that step, including writing the change summary, verification notes, and linked Issue reference.

How to automatically delete a branch after merging a pull request?

After the PR merges successfully, delete the local branch with 'git branch -d' and remove any associated git worktree with 'git worktree remove'. This Skill performs both cleanup steps automatically once the merge completes.

What should a good pull request comment include?

A good PR comment states what the code changes do, how the changes were verified or tested, and which Issue the work relates to. This Skill generates that comment content as part of creating the pull request.

Can I close GitHub Issues automatically when merging a PR?

Yes, referencing an Issue in the PR or using the GitHub API can close it on merge. This Skill additionally writes discussion details, design decisions, and background context into the Issue comment before closing it.

When should I not use automated branch cleanup?

Avoid automatic deletion when the branch is shared with teammates, still needed for follow-up fixes, or when the merge has not been confirmed successful. This Skill only deletes the branch and worktree after the merge succeeds.