GitFlow

Automatically monitor CI/CD pipeline status of new push across GitHub and GitLab in one place. Auto DevOps this is the way 🦞!

Security Scan

The skill's description promises automatic, cross‑repo CI/CD monitoring, but the provided instructions only show manual CLI commands and a user-added git alias — and the skill fails to declare required tooling; these mismatches warrant caution.

Purpose & Capability

The README/SKILL.md claim 'automatically monitor CI/CD pipeline status of new push' across GitHub and GitLab, but there is no mechanism for background monitoring, webhooks, or a service that watches remote pushes. The only automation described is a local git alias that the user must add and run manually after pushing. Also, the instructions depend on 'gh' and 'glab' CLIs (and git) but the skill package metadata did not declare any required binaries — an inconsistency.

Instruction Scope

Instructions are limited to running git, gh, and glab commands and adding a git alias to ~/.gitconfig that runs a shell snippet after push. This is within the stated goal (monitoring pipeline status after a push) but the alias uses a shell invocation ('!f() { ... }; f') which will execute arbitrary shell commands when invoked — this is expected for a git alias but users should review it before adding to their config. The SKILL.md does not instruct reading unrelated files or exfiltrating data.

Install Mechanism

No install spec and no code files — the skill is instruction-only. That reduces risk because nothing is automatically downloaded or written by the skill package itself.

Credentials

The skill requests no environment variables or credentials in metadata, which matches the absence of code. However, practical use requires authenticated 'gh' and/or 'glab' sessions (tokens/configs) to access workflows/pipelines. The skill does not mention or declare that those CLIs and credentials must exist, which is a documentation/metadata omission that could confuse users.

Persistence & Privilege

No special persistence privileges are requested (always is not set, model invocation flags are default). The skill cannot be invoked autonomously by the model beyond the normal platform behavior.

What to consider before installing

This skill is instruction-only and doesn't install anything, but it is inconsistent with its marketing. Before using it: (1) understand it does not create a background watcher or webhook — it only documents CLI commands and offers a manual git alias that you must add yourself; (2) inspect the alias carefully before adding it to ~/.gitconfig since git aliases starting with '!' run shell code; (3) ensure you have and are logged into the 'gh' and/or 'glab' CLIs (they are required in practice even though not declared); (4) if you need true automatic monitoring across pushes (server-side), use webhooks or a CI integration rather than this local alias; (5) if you want the package to be more trustworthy, ask the publisher to declare required binaries and explain authentication requirements and provide a real homepage/source for review.

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

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

---