Verified:GitHub

publishing-git-review-requests

Commits, pushes, and opens GitHub PRs or GitLab MRs for local changes.

Updated Apr 26, 2026

Search Tags:#git #code review #pull request #github #push #gitlab #merge request

One-click install

npx skills add https://github.com/Jin9/skillify-foundation --skill publishing-git-review-requests-jin9

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: publishing-git-review-requests
Source: https://github.com/Jin9/skillify-foundation/tree/main/plugins/ticket-to-mr/skills/publishing-git-review-requests
Command: npx skills add https://github.com/Jin9/skillify-foundation --skill publishing-git-review-requests-jin9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Moving a local change into a hosted code review involves many error-prone steps: staging the right files, configuring remotes, pushing branches, and opening a PR or MR. This Skill orchestrates that entire flow on GitHub or GitLab while requiring explicit confirmation before every mutating command, protecting uncommitted work and preventing destructive operations. ## Core Features & Use Cases - End-to-end publishing workflow: Classifies the request (commit-only, remote setup, push-only, review request, or full workflow), inspects repository state, plans mutations, and executes in the safest order. - Provider-aware operation: Infers GitHub (`gh`) or GitLab (`glab`) from remotes and wording, asks when ambiguous, and defaults new hosted repositories to private visibility. - Safety guardrails: Enforces a confirmation boundary for all mutating commands, preserves unrelated dirty files, refuses destructive operations like force-push without explicit approval, and never prints tokens or credentials. - Use Case: You finished a bug fix on a local branch with no remote configured. Ask to "create remote and push, then open an MR" and the Skill verifies state, proposes each command for approval, creates a private GitLab project, pushes with upstream tracking, and opens the MR with a structured description. ## Quick Start Ask the agent to commit my current changes, push this branch to GitHub, and open a pull request against the main branch.

Frequently Asked Questions about publishing-git-review-requests

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

FAQPage Schema

How do I push a local branch and open a pull request on GitHub?▼

The Skill inspects your repo state, stages only the intended files, commits with an approved message, pushes the branch with upstream tracking, and runs gh pr create against the approved base branch. Every mutating command requires your explicit confirmation first.

How to create a GitLab merge request from the command line?▼

The Skill uses the glab CLI to create merge requests after pushing your branch. It infers GitLab from gitlab.com remotes or MR terminology, verifies authentication with glab auth status, and includes summary, validation, and risk notes in the MR body.

Does it work with both GitHub and GitLab remotes?▼

Yes, it supports GitHub via gh and GitLab via glab, inferring the provider from remote URLs or your wording. If the provider is ambiguous, it asks you to choose before planning any mutation, and it never silently converts one provider's remote into the other.

Will it force-push or overwrite my existing remote configuration?▼

No. Force-push, hard resets, branch deletion, and amending published commits are refused unless you explicitly request that exact destructive action. If an existing origin points elsewhere, it surfaces the mismatch and asks before changing anything.

What happens to my uncommitted unrelated changes during the commit step?▼

Unrelated dirty files are left unstaged and preserved. The Skill stages only the explicit paths required for your request and reports any intentionally untouched files in the final execution summary.

When should I not use this git publishing workflow?▼

Do not use it for release publishing, deployments, CI pipeline authoring, CI security review, Bitbucket repositories, broad repository administration, or rewriting published history. It is scoped to one local change and one review request.