Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Automatically monitor CI/CD pipeline status of new push across GitHub and GitLab in one place. Auto DevOps this is the way ๐ฆ!
Automatically monitor CI/CD pipeline status of new push across GitHub and GitLab in one place. Auto DevOps this is the way ๐ฆ!
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
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.
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
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.
Use the gh CLI tool to fetch workflow status after pushing:
gh run list Lists recent workflow runs for the repository.
gh run list --branch $(git branch --show-current) --limit 1 Shows the most recent workflow run for the current branch.
gh run view <run-id> Displays detailed information about a specific workflow run.
gh run watch Watches the most recent run until completion, streaming status updates.
gh run view <run-id> --log Displays the full logs for a workflow run.
gh run view <run-id> --log-failed Shows only the logs from failed jobs.
gh run rerun <run-id> --failed Reruns only the failed jobs from a workflow run.
Use the glab CLI tool to fetch pipeline status after pushing:
glab ci status Shows the status of the most recent pipeline on the current branch.
glab ci view Opens an interactive view of the current pipeline with job details.
glab ci list Lists recent pipelines for the repository.
glab ci view <pipeline-id> View details of a specific pipeline by ID.
glab ci status --live Continuously monitors the pipeline status until completion.
glab ci trace <job-id> Streams the logs of a specific job.
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"
git pushflow git pushflow origin main
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.