Verified:GitHub

vcs-change-request

Create standardized GitHub pull requests and GitLab merge requests with Markdown descriptions.

Updated Feb 18, 2026

Search Tags:#git #code review #version control #pull request #developer workflow #merge request

Ready to run

npx skills add https://github.com/diegocanepa/agent-skills --skill vcs-change-request

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vcs-change-request
Source: https://github.com/diegocanepa/agent-skills/tree/main/skills/vcs-change-request
Command: npx skills add https://github.com/diegocanepa/agent-skills --skill vcs-change-request

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of Pull Requests (GitHub) and Merge Requests (GitLab) by ensuring clear, actionable, and standardized descriptions, reducing review time and improving code quality.

Core Features & Use Cases

Platform Detection: Automatically identifies whether to create a PR or MR.
Contextual Drafting: Gathers information about changes and links to relevant issues.
Standardized Formatting: Enforces Markdown, English-only, and emoji usage based on best practices.
Use Case: When you've completed a new feature, this Skill will help you draft a PR description that includes a summary, related issue, type of change, and specific modifications, ready for review.

Quick Start

Use the vcs-change-request skill to create a new pull request for the current branch.

Frequently Asked Questions about vcs-change-request

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

FAQPage Schema

How do I automate pull request descriptions for GitHub and GitLab?▼

You can automate pull request descriptions by using a tool that detects your VCS platform and drafts Markdown templates. It standardizes titles, links issues, and structures summaries to reduce manual formatting and code review time.

What should a standardized merge request description include?▼

A standardized merge request description should include a summary of changes, related issue links, the type of change, and specific modifications. Using Markdown formatting with clear guidelines ensures the description is concise and ready for review.

Does this PR drafting tool work with both GitHub and GitLab?▼

Yes, the tool automatically detects whether you are working on GitHub or GitLab. It adapts the output to create either a Pull Request or Merge Request, applying the appropriate formatting and templates for your specific platform.

How do I format a merge request title for better code review workflows?▼

Formatting a merge request title for better code review workflows requires adhering to specific templates and guidelines. The tool enforces English-only titles and standardized structures to ensure clarity and conciseness for reviewers.

When do I need to use a template for pull requests?▼

You need a pull request template when you want to streamline code review workflows and improve code quality. Using a template ensures your descriptions are clear, actionable, and properly linked to relevant issues before submitting changes.