rai-bugfix-close

Push a verified bug branch and create a GitLab merge request.

71|8|Updated Feb 13, 2026

Search Tags:#git #gitlab #bugfix #branch-management #continuous-integration #merge-request #glab

One-click install

npx skills add https://github.com/humansys/raise --skill rai-bugfix-close

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: rai-bugfix-close
Source: https://github.com/humansys/raise/tree/main/packages/raise-cli/src/raise_cli/skills_base/rai-bugfix-close
Command: npx skills add https://github.com/humansys/raise --skill rai-bugfix-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures completed bug work is published to the team by pushing the bug branch, creating a GitLab merge request targeting the development branch, and cleaning up the local branch only after required artifacts are present.

Core Features & Use Cases

Verifies completeness of required artifacts (scope.md, analysis.md, plan.md, retro.md) and a clean working tree before closing.
Pushes the bug branch and creates a merge request using the glab CLI, with a fallback to provide a push URL for manual MR creation.
Enforces strict scope constraints to avoid modifying files outside the bug branch and prevents local merges to the development branch.
Use case: finalize a developer's bugfix by ensuring governance artifacts exist, opening the MR for review, and removing the local branch.

Quick Start

Push the current bug branch, create a GitLab merge request targeting the development branch, and delete the local bug branch after verifying all required artifacts and a clean working tree.

Frequently Asked Questions about rai-bugfix-close

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

FAQPage Schema

How do I create a GitLab merge request for a bugfix branch from the command line?▼

To create a GitLab merge request for a bugfix branch, push the verified branch and use the glab CLI to open an MR targeting the development branch. If glab is unavailable, the system provides a push URL for manual MR creation.

What artifacts are required before closing a bugfix branch?▼

Before closing a bugfix branch, required artifacts include scope.md, analysis.md, plan.md, and retro.md. The process verifies their presence alongside a clean working tree to ensure governance before opening the merge request.

How do I safely delete a local bug branch after pushing to GitLab?▼

To safely delete a local bug branch after pushing to GitLab, ensure the working tree is clean and all required artifacts are verified. The branch is removed locally only after the merge request is successfully created targeting the development branch.

Does the bugfix merge request process allow direct merges to the development branch?▼

No, the bugfix merge request process prevents direct merges to the development branch. It enforces strict scope constraints to avoid modifying files outside the bug branch and ensures changes go through MR review.

What branch naming convention is required to create a bugfix merge request?▼

The required branch naming convention to create a bugfix merge request is bug/raise-{N}/{slug}. Branches must match this pattern to trigger the automated MR creation and local branch cleanup workflow.

Why does my bug branch merge request fail to close the local branch?▼

Your bug branch merge request fails to close the local branch if the working tree is unclean or required artifacts like scope.md and plan.md are missing. A clean state is mandatory for local branch removal.