Verified:GitHub

git-workflow

Automates Git feature branch creation, Conventional Commit staging, and GitLab push workflows.

Updated Aug 15, 2026

Search Tags:#git #version control #conventional commits #gitlab #feature branch #merge request #git push

One-click install

npx skills add https://github.com/jacksonlee-tw/mystock-vue --skill git-workflow-jacksonlee-tw

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/jacksonlee-tw/mystock-vue/tree/main/mystock-analysis/.github/skills/git-workflow
Command: npx skills add https://github.com/jacksonlee-tw/mystock-vue --skill git-workflow-jacksonlee-tw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing development or testing, developers repeatedly perform the same manual Git steps: creating a properly named feature branch, staging changed files, writing a Conventional Commit message, and pushing to GitLab. This Skill automates that entire sequence with consistent naming rules and safety checks. ## Core Features & Use Cases - Standardized Branch Naming: Automatically generates branches in the format `feature/<module>-<type>-<YYYYMMDD>`, with automatic sequence suffixes when duplicates exist. - Conventional Commit Enforcement: Maps work types (backend, frontend, test, docs) to commit types (`feat`, `test`, `docs`, `fix`) with module-based scopes. - Sensitive File Detection: Warns before pushing files like `.env`, `.key`, `password*`, or `kamacfg.ini` that may leak credentials. - Merge Request Link Generation: Parses the GitLab remote URL and outputs a ready-to-click Merge Request creation link. - Use Case: After a backend agent finishes a FastAPI module, say "upload to GitLab" and the Skill creates `feature/manual-card-backend-20260323`, commits 15 changed files with a Conventional Commit message, pushes to origin, and prints the MR link. ## Quick Start Tell the assistant to commit my current changes and push them to GitLab on a new feature branch.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I automate Git branch creation and push to GitLab?▼

Use this Skill to scan uncommitted changes, create a feature branch named feature/<module>-<type>-<date>, stage all files with git add -A, commit using Conventional Commit format, and push to the GitLab remote with upstream tracking.

How to write Conventional Commit messages for feature branches?▼

Conventional Commits use the format type(scope): description, where type is feat, fix, test, docs, or refactor, and scope is the module name in kebab-case. For example: feat(manual-card): add backend module code.

What branch naming convention works for GitLab feature workflows?▼

This Skill uses feature/<module>-<type>-<YYYYMMDD>, where type reflects the work origin such as backend, frontend, test, or docs. If the branch already exists, a numeric suffix like -2 or -3 is appended automatically.

Does it prevent committing sensitive files like .env or keys?▼

Yes. Before pushing, the Skill scans staged changes for patterns like *.env, *.key, *.pem, *password*, *secret*, and kamacfg.ini, then warns the user and suggests adding them to .gitignore instead.

What happens if the remote branch already exists on GitLab?▼

The Skill detects the naming conflict and offers options: automatically append a sequence number to the branch name, switch to the existing branch to continue work, or cancel the operation entirely.

Why does git push fail with authentication errors on GitLab?▼

Push failures usually mean missing credentials or insufficient GitLab permissions. The Skill suggests running git config credential.helper store to cache credentials, then retrying the push after verifying account access.