git-workflow

Orchestrate git commits, pushes, pull requests, CI monitoring, and merges.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/eumemic/dev-skills --skill git-workflow-eumemic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/eumemic/dev-skills/tree/main/skills/git-workflow
Command: npx skills add https://github.com/eumemic/dev-skills --skill git-workflow-eumemic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes uncertainty and mistakes from git-based development workflows by guiding commit, push, pull request creation, CI monitoring, review requests, and merges with explicit safety checks.

Core Features & Use Cases

  • Atomic commits with cleanup: Produces clean, logically staged commits and removes debug noise before committing.
  • PR lifecycle orchestration: Creates PRs, monitors checks until green, requests review when appropriate, and handles review follow-ups.
  • Merge with guardrails: Squash-merges only when prerequisites are satisfied (no uncommitted changes, CI passing, mergeable status).

Use Case: You implement a small feature, want a PR with a test plan, then need to fix CI until it turns green and merge safely.

Quick Start

Ask the AI to "fix CI and merge the PR" to monitor checks, apply fixes, and squash-merge when everything is passing.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I automate a git pull request workflow from commit to merge?

To automate a git pull request workflow, you orchestrate commits, push changes, create PRs, monitor CI checks, request reviews, and squash merge only when CI passes and the branch is mergeable. This ensures clean history and consistent PR metadata.

How do I fix CI failures and merge a pull request safely?

To fix CI failures and merge safely, you monitor GitHub checks, apply remediation commits until the status turns green, and verify merge prerequisites like no uncommitted changes and mergeable status before performing a squash merge.

What is the safest way to squash merge a git branch without bypassing pre-commit hooks?

The safest way to squash merge a git branch is by enforcing safety requirements that prevent bypassing pre-commit hooks, avoid force pushes, and verify merge prerequisites using git status and GitHub checks before completing the merge.

How do I create atomic commits and clean up debug noise before pushing to GitHub?

To create atomic commits and clean up debug noise, you logically stage changes and remove debug artifacts before committing, ensuring that the pushed history remains clean and focused on the feature work.

Can I use gh CLI to monitor CI checks and handle pull request review follow-ups?

Yes, you can use gh CLI to monitor CI checks, request reviews when appropriate, and handle review follow-ups by orchestrating the PR lifecycle until all checks pass and the branch is ready for a safe merge.

Why should I avoid force pushes when orchestrating a git merge workflow?

You should avoid force pushes in a git merge workflow because enforcing safety requirements prevents history corruption, ensuring that merge prerequisites are verified through git status and CI checks pass before squash merging.