skills.rest
MohitVachhani
MohitVachhaniCOMMUNITY
Explore all skills by this author →
𝕏@mohitvachhani55GitHub

mr-writeup

Generate concise MR titles and structured descriptions with code logic and schema notes.

Updated Mar 25, 2026
Search Tags:#workflow#documentation#frontend#backend#code-review#merge-request#mr-writeup
One-click install
npx skills add https://github.com/MohitVachhani/personal-claude-skill --skill mr-writeup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mr-writeup
Source: https://github.com/MohitVachhani/personal-claude-skill/tree/main/mr-writeup
Command: npx skills add https://github.com/MohitVachhani/personal-claude-skill --skill mr-writeup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear and structured merge request (MR) descriptions is time-consuming and error-prone; this Skill automates the creation of concise MR titles and comprehensive descriptions to speed up code reviews.

Core Features & Use Cases

  • Generate a concise MR title
  • Create a structured MR description with feature-wise changes, code logic summary, bug fixes, and DB/schema notes
  • Use this for merge requests or pull requests to improve review efficiency

Quick Start

Provide a concise MR writeup for the changes in your current branch.

Frequently Asked Questions about mr-writeup

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

FAQPage Schema
How do I generate a structured merge request description from my code changes?▼

You can generate a structured merge request description by processing your branch changes to automatically create a concise title and a reviewer-friendly document. This output highlights feature-wise changes, code logic summaries, bug fixes, and DB/schema notes.

What should a pull request writeup include for frontend and backend changes?▼

A pull request writeup for frontend and backend changes should include feature-wise modifications, code logic summaries, bug fixes, and DB/schema notes. It maps diffs into a clean document highlighting impact areas, testing notes, and follow-up actions.

Can I automate MR title generation for both frontend and backend merge requests?▼

Yes, you can automate MR title generation for both frontend and backend merge requests. The automation analyzes your code diffs to produce a concise title alongside a structured description featuring schema notes and testing details.

How do I document database schema changes in a pull request description?▼

To document database schema changes in a pull request description, the generated writeup includes a dedicated section for DB/schema notes. This ensures reviewers immediately see database impact areas alongside the code logic summaries and feature changes.

What is the best way to speed up code review with structured documentation?▼

The best way to speed up code review with structured documentation is to automate MR writeups that map diffs into a clean, reviewer-friendly format. This highlights impact areas, bug fixes, and follow-up notes efficiently for reviewers.

Related Skills

Explore More Software Engineering Skills→
jmaglyjmagly
175

traceability-check

Maps requirements to code and tests, computes coverage gaps and generates a traceability report.

Community
Intermediate
hua-banghua-bang
27

mr-generator

Generate MR titles and descriptions from code diffs for GitHub and GitLab.

Community
Intermediate
superfhpsuperfhp

requesting-code-review

Automate pre-commit code review by scanning git diffs for security vulnerabilities and quality issues.

Community
Advanced
yasudaProductyasudaProduct
1

commit-helper

Enforce typed Git commit messages and PR creation workflows.

Community
Intermediate