git-workflow
git-workflow provides structured guidance on writing effective commit messages using conventional formats, organizing branches by type and purpose, and managing pull requests at scale. It covers atomic commits, conflict resolution, and enforcing standards through git hooks.
git-workflow teaches conventional commit formats, branching strategies, and pull request workflows for maintaining clean git history.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-05-16
git-workflow teaches conventional commit formats, branching strategies, and pull request workflows for maintaining clean git history. git-workflow provides structured guidance on writing effective commit messages using conventional formats, organizing branches by type and purpose, and managing pull requests at scale. It covers atomic commits, conflict resolution, and enforcing standards through git hooks.
Use it when
- git-workflow recommends establishing consistent branching conventions tied to purpose: feature branches (feature/description).
- git-workflow advocates for small, focused pull requests that address a single concern, making code review faster and more effective.
Verify before relying
Read SKILL.md below before installing (37 files). Open directory: indexed for reading, not audited.
Install
AsyrafHussin/agent-skills/git-workflow
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What are git best practices for commit messages?
git-workflow emphasizes conventional commits format as the foundation for effective commit messages. Structure messages with a type (feat, fix, docs, etc.), optional scope, and clear description. Keep the subject line under 50 characters, use imperative mood, and separate the body with a blank line. This approach enables automated changelog generation and improves team collaboration.
How should git-workflow handle branching strategy and naming?
git-workflow recommends establishing consistent branching conventions tied to purpose: feature branches (feature/description), bugfix branches (bugfix/description), and release branches (release/version). Naming consistency helps teams quickly understand branch intent. Pair this with a clear strategy—gitflow for complex releases or github flow for continuous deployment—based on your team's needs.
What does git-workflow say about pull request workflow?
git-workflow advocates for small, focused pull requests that address a single concern, making code review faster and more effective. Include a descriptive PR template, link related issues, and keep discussions constructive. This workflow improves code quality and team communication while reducing merge conflicts and review bottlenecks.
How does git-workflow keep git history clean?
git-workflow teaches atomic commits—small, logical units that each represent one change—and interactive rebase for cleanup before merging. Choose merge strategies carefully: rebase for linear history or merge commits for explicit integration points. Clean history makes debugging easier and improves project maintainability.
Can git-workflow enforce commit standards automatically?
Yes. git-workflow covers setting up git hooks using tools like Husky and commitlint to validate commits against your standards before they're pushed. Automated enforcement ensures team consistency without manual review, catching formatting issues and preventing non-compliant commits from entering the repository.
What's the difference between rebase vs merge in git-workflow?
git-workflow explains that rebase rewrites history for a linear, clean timeline—ideal for feature branches before merging to main. Merge commits preserve integration history and are safer for shared branches. Choose based on your workflow: rebase for local cleanup, merge for permanent integration points and collaborative branches.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Git Workflow
Git best practices, commit conventions, branching strategies, and pull request workflows. Guidelines for maintaining a clean, useful git history.
When to Apply
Reference these guidelines when: - Writing commit messages - Creating branches - Setting up git workflows - Reviewing pull requests - Maintaining git history
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Commit Messages | CRITICAL | commit- |
| 2 | Branching Strategy | HIGH | branch- |
| 3 | Pull Requests | HIGH | pr- |
| 4 | History Management | MEDIUM | history- |
| 5 | Collaboration | MEDIUM | collab- |
Quick Reference
1. Commit Messages (CRITICAL)
commit-conventional- Use conventional commitscommit-atomic- Atomic
(truncated - see the full file via the links below)
File tree — 15 files
skills/git-workflow/AGENTS.md
skills/git-workflow/README.md
skills/git-workflow/SKILL.md
skills/git-workflow/metadata.json
skills/git-workflow/rules/_sections.md
skills/git-workflow/rules/_template.md
skills/git-workflow/rules/branch-delete-merged.md
skills/git-workflow/rules/branch-feature-workflow.md
skills/git-workflow/rules/branch-main-protected.md
skills/git-workflow/rules/branch-monorepo.md
skills/git-workflow/rules/branch-naming-convention.md
skills/git-workflow/rules/branch-release-strategy.md
skills/git-workflow/rules/branch-short-lived.md
skills/git-workflow/rules/branch-workflow-strategies.md
skills/git-workflow/rules/collab-code-review.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Learn and apply git commit message conventions and best practices”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Git Hygiene Enforcer helps teams standardize development practices by automating commit validation, branch naming enforcement, and pull request workflows. It provides ready-to-use configurations for commit hooks, branch protection rules, and CI/CD checks that maintain code quality without manual oversight.
This skill teaches standardized git practices including conventional commit formatting, semantic branch naming patterns, and merge strategy selection. It provides templates and guidelines to maintain consistency across teams while enabling automated changelog generation and reducing code review friction.
This skill guides you through structured Git workflows for team collaboration, covering branching strategies like trunk-based development, GitHub Flow, and GitFlow. Learn to enforce code quality with conventional commits, Git hooks, and branch protection rules, plus manage monorepos with clear ownership patterns.
Conventional Commits helps you write structured, semantic commit messages that enable automated versioning and changelog generation. It guides you through selecting commit types, adding optional scopes, and formatting descriptions in imperative mood, with support for breaking changes and footer tokens.
Adapt Conventional Commits for Chinese development teams with localized type definitions, message templates, and tooling integration. Configure commitlint, husky, and conventional-changelog to enforce consistent commit practices across your team while keeping type keywords in English for tool compatibility.
Configure pre-commit, commit-msg, and pre-push hooks to standardize your team's development workflow. Supports both husky and native git hooks, with built-in linting, code formatting, commit message validation, and secret detection to catch issues before they reach your repository.
More skills Commit Message (unlicensed) · Woocommerce Git Draft Pr (unlicensed) · laravel-best-practices (MIT)