How do I install the Gitflow skill?

Run npx skillmds@latest add modbender/gitflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gitflow safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gitflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gitflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gitflow?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gitflow by modbender — Agent Skill

Name: Gitflow
Rating: 4.666666666666667 (3 reviews)
Author: modbender

File contents

GitFlow — OpenClaw Skill

Overview

GitFlow is an OpenClaw skill that automates code pushes and provides real-time CI/CD pipeline status monitoring for GitHub and GitLab repositories. It streamlines developer workflows by reducing context switching between repositories and pipeline dashboards.

The skill can automatically push changes and report pipeline results, enabling faster feedback and smoother deployments.

Features

GitFlow can:

Push local commits automatically
Trigger remote CI/CD pipelines
Fetch pipeline status and results
Report build success or failure
Display pipeline URLs and logs
Monitor multiple repositories

Typical Workflow

Developer commits changes locally.
GitFlow pushes changes automatically or on command.
CI/CD pipeline runs remotely.
Skill reports pipeline status.
Developer receives build/deploy feedback instantly.

GitHub CLI Commands

Use the gh CLI tool to fetch workflow status after pushing:

Check Workflow Run Status

gh run list

Lists recent workflow runs for the repository.

View Latest Run for Current Branch

gh run list --branch $(git branch --show-current) --limit 1

Shows the most recent workflow run for the current branch.

View Run Details

gh run view <run-id>

Displays detailed information about a specific workflow run.

Watch Run in Real-Time

gh run watch

Watches the most recent run until completion, streaming status updates.

View Run Logs

gh run view <run-id> --log

Displays the full logs for a workflow run.

View Failed Job Logs

gh run view <run-id> --log-failed

Shows only the logs from failed jobs.

Rerun Failed Jobs

gh run rerun <run-id> --failed

Reruns only the failed jobs from a workflow run.

GitLab CLI Commands

Use the glab CLI tool to fetch pipeline status after pushing:

Check Pipeline Status

glab ci status

Shows the status of the most recent pipeline on the current branch.

View Pipeline Details

glab ci view

Opens an interactive view of the current pipeline with job details.

List Recent Pipelines

glab ci list

Lists recent pipelines for the repository.

View Specific Pipeline

glab ci view <pipeline-id>

View details of a specific pipeline by ID.

Watch Pipeline in Real-Time

glab ci status --live

Continuously monitors the pipeline status until completion.

Get Pipeline Job Logs

glab ci trace <job-id>

Streams the logs of a specific job.

Post-Push Hook Example

Git doesn't have a native post-push hook, but you can create a git alias to automatically monitor pipeline status after pushing.

Add this to your ~/.gitconfig:

[alias]
    pushflow = "!f() { \
        git push \"${1:-origin}\" \"${2:-$(git branch --show-current)}\"; \
        url=$(git remote get-url \"${1:-origin}\"); \
        if echo \"$url\" | grep -q 'github.com'; then \
            sleep 3 && gh run watch; \
        elif echo \"$url\" | grep -q 'gitlab'; then \
            sleep 3 && glab ci status --live; \
        fi; \
    }; f"

Usage

git pushflow
git pushflow origin main

---name: gitflowdescription: Automatically monitor CI/CD pipeline status of new push across GitHub and GitLab in one place. Auto DevOps this is the way 🦞!--- # GitFlow — OpenClaw Skill ## Overview **GitFlow** is an OpenClaw skill that automates code pushes and provides real-time CI/CD pipeline status monitoring for GitHub and GitLab repositories. It streamlines developer workflows by reducing context switching between repositories and pipeline dashboards. The skill can automatically push changes and report pipeline results, enabling faster feedback and smoother deployments. ## Features GitFlow can: - Push local commits automatically - Trigger remote CI/CD pipelines - Fetch pipeline status and results - Report build success or failure - Display pipeline URLs and logs - Monitor multiple repositories ## Typical Workflow 1. Developer commits changes locally. 2. GitFlow pushes changes automatically or on command. 3. CI/CD pipeline runs remotely. 4. Skill reports pipeline status. 5. Developer receives build/deploy feedback instantly. ## GitHub CLI Commands Use the `gh` CLI tool to fetch workflow status after pushing: ### Check Workflow Run Status ```bash gh run list ``` Lists recent workflow runs for the repository. ### View Latest Run for Current Branch ```bash gh run list --branch $(git branch --show-current) --limit 1 ``` Shows the most recent workflow run for the current branch. ### View Run Details ```bash gh run view <run-id> ``` Displays detailed information about a specific workflow run. ### Watch Run in Real-Time ```bash gh run watch ``` Watches the most recent run until completion, streaming status updates. ### View Run Logs ```bash gh run view <run-id> --log ``` Displays the full logs for a workflow run. ### View Failed Job Logs ```bash gh run view <run-id> --log-failed ``` Shows only the logs from failed jobs. ### Rerun Failed Jobs ```bash gh run rerun <run-id> --failed ``` Reruns only the failed jobs from a workflow run. --- ## GitLab CLI Commands Use the `glab` CLI tool to fetch pipeline status after pushing: ### Check Pipeline Status ```bash glab ci status ``` Shows the status of the most recent pipeline on the current branch. ### View Pipeline Details ```bash glab ci view ``` Opens an interactive view of the current pipeline with job details. ### List Recent Pipelines ```bash glab ci list ``` Lists recent pipelines for the repository. ### View Specific Pipeline ```bash glab ci view <pipeline-id> ``` View details of a specific pipeline by ID. ### Watch Pipeline in Real-Time ```bash glab ci status --live ``` Continuously monitors the pipeline status until completion. ### Get Pipeline Job Logs ```bash glab ci trace <job-id> ``` Streams the logs of a specific job. --- ## Post-Push Hook Example Git doesn't have a native post-push hook, but you can create a git alias to automatically monitor pipeline status after pushing. Add this to your `~/.gitconfig`: ```ini [alias] pushflow = "!f() { \ git push \"${1:-origin}\" \"${2:-$(git branch --show-current)}\"; \ url=$(git remote get-url \"${1:-origin}\"); \ if echo \"$url\" | grep -q 'github.com'; then \ sleep 3 && gh run watch; \ elif echo \"$url\" | grep -q 'gitlab'; then \ sleep 3 && glab ci status --live; \ fi; \ }; f" ``` ### Usage ```bash git pushflow git pushflow origin main ``` ---

Frequently asked questions

Gitflow