git-workflow

Automate git status, staging, commit, push, and MR generation on non-master branches.

27|1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/hua-bang/pulse-agent --skill git-workflow-hua-bang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/hua-bang/pulse-agent/tree/main/.pulse-coder/skills/git-workflow
Command: npx skills add https://github.com/hua-bang/pulse-agent --skill git-workflow-hua-bang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the git workflow for the current branch, automating the addition, commit, push, and MR generation process when needed.

Core Features & Use Cases

  • Automated Git Workflow: Handles the full workflow including status check, staging, committing, pushing, and running MR generation.
  • MR Generation: Automatically generates merge requests for non-master or main branches after push.
  • Customizable: Offers both end-to-end and selective workflows, allowing staging of specific paths and splitting into multiple commits.

Quick Start

To start the workflow, simply execute: git status to check your branch status, then git add -A to stage changes, followed by git commit -m "Your commit message" and git push to push the changes and generate an MR if needed.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I automate my git workflow from staging to MR generation?

To automate your git workflow, the Skill handles the full process from checking git status, staging changes, committing, pushing, to generating a merge request automatically for non-master branches.

Can I generate merge requests automatically after a git push?

Yes, you can generate merge requests automatically after a git push. The Skill is designed to create MRs for non-master or main branches once your code changes are pushed to the remote repository.

Does the automated git workflow support staging specific file paths?

Yes, the automated git workflow supports staging specific paths. It offers customizable selective workflows, allowing you to stage targeted files and split changes into multiple commits rather than staging everything.

Can I use this to push commits directly to the master or main branch?

No, you cannot use this to push commits directly to the master or main branch. The Skill explicitly handles non-master or main branches only to protect your primary codebase from automated pushes.

What is the best way to manage code changes and split commits across different paths?

The best way to manage code changes and split commits is using a customizable git workflow that allows selective staging of specific paths, enabling you to separate modifications into multiple targeted commits before pushing.