skills.rest
baphled
baphledCOMMUNITY
Explore all skills by this author →
Website𝕏@baphledGitHub

pre-merge

Execute a pre-merge validation checklist for Pull Requests.

1|Updated Mar 5, 2026
Search Tags:#git#quality assurance#ci/cd#checklist#merge#pr
One-click install
npx skills add https://github.com/baphled/dotopencode --skill pre-merge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-merge
Source: https://github.com/baphled/dotopencode/tree/main/skills/pre-merge
Command: npx skills add https://github.com/baphled/dotopencode --skill pre-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the merging of low-quality or incomplete Pull Requests by enforcing a comprehensive checklist before the final merge action.

Core Features & Use Cases

  • Pre-merge Validation: Runs a detailed checklist covering branch status, automated checks, code quality, compatibility, and deployment readiness.
  • Risk Mitigation: Catches issues that might be missed by code review or CI, ensuring backward compatibility and clean history.
  • Use Case: Before merging a critical feature to the main branch, use this Skill to confirm all review comments are addressed, CI is green, and documentation is updated.

Quick Start

Run the pre-merge checklist to ensure the current branch is ready for merging.

Frequently Asked Questions about pre-merge

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

FAQPage Schema
How do I ensure PR quality before merging into the main branch?▼

To ensure PR quality before merging, execute a comprehensive pre-merge validation checklist covering branch rebasing, CI status, test coverage, API stability, and documentation updates to guarantee safe code integration.

What should a pre-merge checklist for CI/CD include to prevent low-quality pull requests?▼

A pre-merge checklist for CI/CD should include branch status verification, automated check validation, code hygiene review, backward compatibility checks, and deployment readiness confirmation to prevent merging incomplete pull requests.

How do I validate branch rebasing and test coverage before a git merge?▼

Validate branch rebasing and test coverage before a git merge by running a pre-merge validation process that catches missed issues, enforces clean history, and confirms all review comments are addressed.

Does pre-merge validation check for API stability and documentation updates?▼

Yes, pre-merge validation checks for API stability and documentation updates as part of its comprehensive checklist to mitigate risks and ensure backward compatibility before final code integration.

When do I need to run a pre-merge checklist for pull requests?▼

You need to run a pre-merge checklist for pull requests before merging critical features to the main branch, ensuring all CI checks are green, code quality is verified, and deployment readiness is confirmed.

Can I use pre-merge validation to catch issues missed by code review and CI?▼

Yes, you can use pre-merge validation to catch issues missed by code review or CI, specifically verifying branch rebasing, code hygiene, API stability, and documentation updates for reliable integration.

Related Skills

Explore More Software Engineering Skills→
bmsull560bmsull560

jr-rebase

Resolves git rebase conflicts in feature branches via guided marker resolution.

Community
Intermediate
tachfineamnaytachfineamnay

Git Workflow & CI/CD

Standardize Git workflows and CI/CD pipelines with Husky and GitHub Actions.

Community
Intermediate
michsindlingermichsindlinger
1

Quality Metrics Skill

Automate code quality tracking and reporting across CI/CD pipelines.

Community
Advanced
jieni777jieni777
1

code-review-checklist

Generate code review checklists covering functionality, security, performance, and maintainability.

Community
Advanced