skills.rest
Anders-planck
Anders-planckCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

source-control

Standardize conventional commits and Git branch workflows.

Updated Apr 20, 2026
Search Tags:#git#code-quality#version-control#conventional-commits#git-hooks#commit-messages#branch-workflow
One-click install
npx skills add https://github.com/Anders-planck/opencode-config --skill source-control-anders-planck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-control
Source: https://github.com/Anders-planck/opencode-config/tree/main/skills/source-control
Command: npx skills add https://github.com/Anders-planck/opencode-config --skill source-control-anders-planck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git projects often suffer from inconsistent commit messages and unclear workflows, making collaboration and history tracking harder. This skill provides a unified set of conventions for commit messages and branch/workflow patterns to improve readability and maintainability.

Core Features & Use Cases

  • Conventional commits format: guidance on types, scopes, bodies, and footers to create semantic, machine-readable messages.
  • Branching and workflow patterns: standardized branch naming and rebase/merge guidance to keep history linear and predictable.
  • Quality and automation practices: use of pre-commit hooks and guidelines to enforce discipline and reduce risky changes.

Quick Start

Start by drafting a conventional commit message (e.g., feat(auth): add login) and follow the branch workflow to create a feature branch from main.

Frequently Asked Questions about source-control

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

FAQPage Schema
What are conventional commits and how do they improve git history?▼

Conventional commits standardize commit messages using structured types, scopes, bodies, and footers to create semantic, machine-readable git history. This format improves readability, maintainability, and collaboration across software development teams.

How do I structure a conventional commit message for a new feature?▼

Structure a conventional commit message by specifying a type, scope, and description, such as feat(auth): add login. You can further include a body and footer to provide context and metadata for machine-readable history tracking.

What is the best way to manage branch workflows for predictable git history?▼

The best way to manage branch workflows is adopting standardized branch naming and applying consistent rebase or merge guidance. This keeps your git history linear and predictable across code bases of varying sizes.

Can I use git hooks to enforce commit message conventions?▼

Yes, you can use pre-commit git hooks to enforce commit message conventions and workflow discipline. Automating these quality practices reduces risky changes and ensures adherence to standardized branching patterns.

Do I need a specific environment to apply these git conventions to my code base?▼

You need a software development environment utilizing git for version control. The conventions apply to code bases of varying sizes and require a YAML frontmatter with name and description and a Markdown body loaded during activation.

Related Skills

Explore More Software Engineering Skills→
semirm-devsemirm-dev

git-conventions

Validate Git branch names and commit messages against project conventions.

Community
Intermediate
daniel-heydari-devdaniel-heydari-dev

changelog-generation

Generate changelogs and enforce semantic versioning from conventional commits.

Community
Intermediate
luongnv89luongnv89
104

devops-pipeline

Automate pre-commit hooks and GitHub Actions for code quality.

Community
Advanced
YomiamyYomiamy
16

分支重命名工具 (gen-rn-br)

Rename local Git branches to YYYYMM format based on last commit date.

Community
Basic