skills.rest
developer239
developer239COMMUNITY
Explore all skills by this author →
WebsiteGitHub

workflow-git-cli

Enforce Git branching, staging, and PR workflows for team consistency.

Updated Mar 20, 2026
Search Tags:#git#workflow#branching#pr#code-review#pull-request#ignore-hygiene
One-click install
npx skills add https://github.com/developer239/marek-opencode --skill workflow-git-cli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-git-cli
Source: https://github.com/developer239/marek-opencode/tree/main/src/skills/workflow-git-cli
Command: npx skills add https://github.com/developer239/marek-opencode --skill workflow-git-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies consistent Git workflows to reduce merge conflicts and miscommunications across teams.

Core Features & Use Cases

  • Enforces a clear branching strategy with naming conventions like feat/, fix/, and chore/ to keep history readable.
  • Provides guidelines for staged commits, focused messages, and PR-first collaboration to speed reviews.
  • Supports daily development routines including syncing main, creating per-ticket branches, and careful PR creation.

Quick Start

Align your local workspace to the main branch, then create and use a feature branch following the feat/ naming convention.

Frequently Asked Questions about workflow-git-cli

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

FAQPage Schema
How do I enforce a consistent git branching strategy for my team?▼

Git branching strategies are enforced using clear naming conventions like feat/, fix/, and chore/ to keep history readable. This approach maintains staged commits, focused messages, and PR-first collaboration to reduce miscommunications and merge conflicts.

What is the best way to structure git commits for pull-request reviews?▼

The best way to structure git commits for PR reviews is to apply staging discipline with focused commit messages. Aligning commits directly with PR creation ensures faster reviews and reduces error cycles across the development team.

How do I create a feature branch from main using Git CLI?▼

To create a feature branch using Git CLI, first sync your local workspace with the main branch, then generate a new branch following the feat/ naming convention to maintain a readable project history.

Why do I need preventative guardrails in my GitHub workflow?▼

Preventative guardrails in your GitHub workflow reduce errors and review cycles by enforcing staging discipline and PR alignment. They prevent miscommunications and merge conflicts across teams before code is merged.

Does this Git workflow approach work for daily team development routines?▼

Yes, this Git workflow approach supports daily team development routines by covering syncing main, creating per-ticket branches, and careful PR creation. It applies to teams using Git CLI or GitHub workflows for consistent collaboration.

What is ignore hygiene in Git and why does it matter?▼

Ignore hygiene in Git ensures proper repository maintenance by preventing unwanted files from entering version control. It is a core part of disciplined workflows that reduce merge conflicts and keep history readable.

Related Skills

Explore More Software Engineering Skills→
VoTruongDanhVoTruongDanh

git-expert

Manage Git repositories, resolve conflicts, and clean history.

Community
Advanced
tachfineamnaytachfineamnay

Git Workflow & CI/CD

Standardize Git workflows and CI/CD pipelines with Husky and GitHub Actions.

Community
Intermediate
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
rmanzokurmanzoku
1

git-branch-review

Review Git branch health and suggest safe merge actions.

Community
Advanced