gitflow

Automate code pushes and monitor CI/CD pipeline status across GitHub and GitLab.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/zangxin75/openclaw-skills --skill gitflow-zangxin75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitflow
Source: https://github.com/zangxin75/openclaw-skills/tree/main/gitflow
Command: npx skills add https://github.com/zangxin75/openclaw-skills --skill gitflow-zangxin75

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the monitoring of CI/CD pipeline statuses across GitHub and GitLab, reducing the need for developers to manually check multiple platforms.

Core Features & Use Cases

  • Automated Push: Facilitates automatic pushing of local commits to remote repositories.
  • CI/CD Monitoring: Tracks and reports the status of CI/CD pipelines triggered by pushes.
  • Cross-Platform Support: Works seamlessly with both GitHub and GitLab.
  • Use Case: A developer pushes code changes and immediately receives a notification about the CI/CD pipeline's success or failure, allowing for rapid iteration.

Quick Start

Use the gitflow skill to push the current branch and watch the CI/CD pipeline status.

Frequently Asked Questions about gitflow

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

FAQPage Schema
How do I monitor CI/CD pipeline status across GitHub and GitLab?

You can monitor CI/CD pipeline status across GitHub and GitLab by integrating with the GitHub CLI (gh) and GitLab CLI (glab) to retrieve real-time build and deployment feedback. This automates status tracking across both platforms without manual checks.

Can I automate code pushes and track the CI/CD pipeline status at the same time?

Yes, you can automate code pushes and track the CI/CD pipeline status simultaneously. The workflow automatically pushes local commits to remote repositories and immediately reports the triggered pipeline's success or failure for rapid iteration.

What is the best way to get real-time feedback on build and deployment processes?

The best way to get real-time feedback on build and deployment processes is to automate pipeline monitoring after pushing code. This provides immediate notifications regarding pipeline success or failure, eliminating the need to manually switch contexts and check platforms.

Do I need the GitHub CLI and GitLab CLI to monitor pipeline statuses?

Yes, you need the GitHub CLI (gh) and GitLab CLI (glab) installed to monitor pipeline statuses. The system integrates directly with these CLIs for status retrieval and reporting across your repositories.

How does cross-platform CI/CD monitoring work for developers using multiple repositories?

Cross-platform CI/CD monitoring works by integrating with both GitHub and GitLab to track pipeline statuses triggered by automated pushes. It consolidates build and deployment feedback into a single workflow, reducing manual platform checking.

Why does tracking CI/CD pipeline success or failure across multiple platforms cause workflow delays?

Tracking CI/CD pipeline success or failure across multiple platforms causes delays because developers must manually check separate interfaces. Automating this status retrieval and reporting process provides immediate feedback, enabling rapid iteration and faster deployment cycles.