skills.rest
edochi
edochiCOMMUNITY
Explore all skills by this author →
𝕏@ChioEdoardoGitHub

commit

Define git commit and branch workflows with conventional commits and PR governance.

27|2|Updated Feb 22, 2026
Search Tags:#git#workflow#commit#branching#code-quality#pull-request#conventional-commits
One-click install
npx skills add https://github.com/edochi/mdvs --skill commit-edochi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/edochi/mdvs/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/edochi/mdvs --skill commit-edochi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent git workflows by guiding users on branching, committing, and PR practices to reduce review friction and drift.

Core Features & Use Cases

  • Branching Strategy: One feature/issue branch per task and protected main to ensure safe integration.
  • Commit Policy: Enforce conventional commits and explicit messages; supports updating TODO statuses via integration with a TODO skill.
  • PR & Review: Standardize PR creation, review steps, and CI gate expectations across teams.

Quick Start

Ask your AI to outline a safe, conventional commit plan and the corresponding branch workflow.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce conventional commits in a feature branch workflow?▼

To enforce conventional commits in a feature branch workflow, establish a policy requiring explicit commit messages and a single feature branch per task to ensure auditability. This approach reduces review friction and prevents drift.

What is the best way to standardize pull request creation and review steps?▼

Standardizing pull request creation involves defining consistent PR governance, review steps, and CI gate expectations across teams. This ensures safe integration into a protected main branch and maintains code quality.

Why should I use feature branches instead of committing directly to main?▼

Using feature branches instead of committing directly to main ensures safe integration and branch hygiene. It isolates development per task, which reduces review friction and maintains consistency across software projects.

Does this git commit workflow execute actions or merge pull requests automatically?▼

This git commit workflow does not execute actions or merge pull requests automatically. It guides users on branching, committing, and PR practices to define a reliable process for auditability and consistency.

How do I update TODO statuses when making conventional commits?▼

You can update TODO statuses when making conventional commits through integration with a TODO skill. This supports the commit policy by linking explicit commit messages directly to task tracking.

Related Skills

Explore More Software Engineering Skills→
chaimtchaimt

speckit-git-initialize

Initialize a Git repository with an initial commit in the current directory.

Community
Intermediate
jkomorosjkomoros
9

git-workflow

Automate Git rebases, conflict resolution, and pull request creation with gh pr.

Community
Intermediate
kys0213kys0213

git

Automate Git branch creation, TODO-based commits, and PR generation.

Community
Intermediate
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced