skills.rest
ademceper
ademceperCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Automate git workflow management and conventional commits for the Merge E-Commerce backend.

Updated Dec 31, 2025
Search Tags:#git#workflow#branching#release-management#code-review#conventional-commits
One-click install
npx skills add https://github.com/ademceper/merge --skill git-workflow-ademceper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ademceper/merge/tree/main/server/.claude/skills/git-workflow
Command: npx skills add https://github.com/ademceper/merge --skill git-workflow-ademceper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates git workflow management and conventional commits for the Merge E-Commerce backend, standardizing processes and reducing manual errors in releases.

Core Features & Use Cases

  • Enforces conventional commit formats with clear type and scope guidance.
  • Provides branch naming conventions and end-to-end Git workflow steps for starting work, daily development, syncing with main, and PR closure.
  • Facilitates consistent release preparation and code-review practices across api, app, domain, infra layers.

Quick Start

Create a feature branch and commit using a conventional message, then push to remote. Example: git checkout -b feature/MERGE-123-user-auth; git commit -m 'feat(auth): add OAuth login'; git push -u origin feature/MERGE-123-user-auth

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce conventional commits in my git workflow?▼

You enforce conventional commits by applying structured messages with specific types and scopes, such as feat(auth) or fix(api). This standardizes feature development and reduces manual release errors.

What is the best way to structure git branch naming for feature development?▼

The best way to structure git branch naming is to use a standardized convention like feature/MERGE-123-user-auth. This ensures clear tracking across api, app, domain, and infra layers during feature development and code review.

How do I manage daily git development and sync with the main branch?▼

Daily git development and syncing with main requires following comprehensive step-by-step workflows. These workflows guide branch creation, daily commits, syncing with the main branch, and PR closure to maintain code review consistency.

Does this git workflow automation support release preparation and code review?▼

Yes, this git workflow automation supports release preparation and code review. It facilitates consistent release practices and code review processes across api, app, domain, and infra layers for backend development.

When do I need automated git workflow management for backend development?▼

You need automated git workflow management for backend development when standardizing processes across multiple layers like api, app, domain, and infra. It guides branch creation, commits, and PR processes to reduce manual release errors.

Related Skills

Explore More Software Engineering Skills→
helderbertohelderberto
114

amend-push

Amend the previous commit and push changes to a remote repository.

Community
Basic
ValyntValynt

deploy-to-staging

Orchestrate staging deployments with safety checks, migrations, and rollback procedures.

Official
Advanced
PouzorPouzor
31

python

Enforce Python code quality with Ruff, Mypy, and Pytest.

Community
Intermediate
vanman2024vanman2024
3

Git Workflows

Standardize git workflows with commit templates, branch helpers, and hook scripts.

Community
Basic