Run any Skill in Manus with one click

merge-request

Stars1

Forks1

UpdatedFebruary 16, 2026 at 10:27

Prepare a merge request or pull request description and copy it to the clipboard. Use when the user asks to create, prepare, or write a merge request, pull request, MR, or PR description, or when summarizing changes for review.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

cboudereau

cboudereau/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	merge-request
description	Prepare a merge request or pull request description and copy it to the clipboard. Use when the user asks to create, prepare, or write a merge request, pull request, MR, or PR description, or when summarizing changes for review.

Merge Request

When to use

User asks to create, prepare, or write a merge request or pull request description
User asks to summarize changes for code review
User mentions "MR", "PR", "merge request", or "pull request"
User wants to copy a description of completed work to the clipboard

Overview

Prepare a merge request description when asked.

Rules

Prepare a markdown format concise merge request description of the work done.
Copy the description content by using clip.exe (windows tool) without introducing complex symbols.

More from this repository

same repository

code-review

cboudereau/dotfiles

Code review principles and checklist for reviewing any codebase regardless of language. Use when the user asks to review code, perform a code review, assess a pull request, or evaluate code quality across design, tests, performance, security, and correctness.

2026-05-201

plan

cboudereau/dotfiles

Planning skill for complex, multi-session work. Use when the user enters plan mode, asks to plan a feature, design a system, create a workspace, write a design doc, or when the problem requires structured analysis before implementation.

2026-05-091

tdd

cboudereau/dotfiles

Test Driven Development methodology with acceptance tests and unit tests. Use when the user asks to write tests, add test coverage, implement a feature using TDD, create a failing test first, or when discussing red-green-refactor, test-first development, or test strategy.

2026-05-031

code-quality

cboudereau/dotfiles

Code quality principles for writing clean, maintainable software. Use when reviewing code, refactoring, discussing best practices, improving readability, reducing complexity, or when the user mentions code quality, clean code, SOLID, DRY, or maintainability.

2026-05-021

dotnet-software-engineer

cboudereau/dotfiles

.NET Software Engineer persona using TDD, Domain Driven Design, and C#. Use when working on .NET, C#, F#, ASP.NET, or dotnet projects, or when the user asks about software architecture, domain modeling, clean architecture, hexagonal architecture, or DDD patterns like aggregates, value objects, entities, and repositories.

2026-05-021

git-conventions

cboudereau/dotfiles

Git command rules, commit message conventions, and safe usage patterns. Use when the user asks to commit, create a branch, check differences, write a commit message, or perform any git operation. Also use when discussing version control workflows or git safety.

2026-05-021

Run any Skill with one click