git-ops

Resolve provider-aware Git review and release workflows for GitHub or GitLab repositories.

1|Updated Feb 8, 2026

Search Tags:#automation #git #github #release #gitlab #pr #mr

One-click install

npx skills add https://github.com/loadinglucian/dotagents --skill git-ops-loadinglucian

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: git-ops
Source: https://github.com/loadinglucian/dotagents/tree/main/skills/git-ops
Command: npx skills add https://github.com/loadinglucian/dotagents --skill git-ops-loadinglucian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates provider-aware Git review and release operations across GitHub and GitLab, reducing manual coordination and errors when managing remotes, default branches, and release artifacts.

Core Features & Use Cases

Canonical remote and default-branch resolution for multi-provider repos.
Review and release automation: create/open PR/MR, squash merges, and publish releases from tags.
Provider detection and safety: fail-closed on ambiguity; supports preview-first flows and remote/provider resolution.

Quick Start

Run the git-ops skill to resolve the default branch and open or create a provider-aware review or release for the current repository.

Frequently Asked Questions about git-ops

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

FAQPage Schema

How do I automate Git review and release workflows across GitHub and GitLab?▼

Provider-aware Git review and release automation resolves remotes, default branches, and artifacts across GitHub and GitLab. It detects the provider, resolves the canonical remote, and orchestrates PR/MR creation, merging, and release publishing to reduce manual coordination.

What is the best way to manage cross-provider Git remotes for pull requests and merge requests?▼

Managing cross-provider Git remotes requires canonical remote and default-branch resolution. The process detects whether a repository is hosted on GitHub or GitLab and applies provider-specific commands for PR or MR lookup and creation to prevent ambiguity.

Can I publish a Git release from a tag across different providers?▼

Yes, you can publish Git releases from tags across different providers. The workflow resolves existing artifact lookups and provider context, then executes release publishing commands tailored to the detected GitHub or GitLab environment with preview-first safety.

Does Git release automation support squash merges and preview-first behavior?▼

Git release automation supports squash merges and preview-first behavior. It safely executes review and merge operations by resolving base and target branches, looking up existing PR/MRs, and previewing actions before applying changes to the repository.

Why does Git provider detection fail on ambiguous remotes during merge operations?▼

Git provider detection fails on ambiguous remotes to ensure safe, fail-closed behavior. When the system cannot definitively resolve the canonical remote or default branch across GitHub and GitLab, it halts operations to prevent incorrect merging or release publishing.