commit

Automate Git workflows with Conventional Commits for branching, staging, PRs, and merges.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sofer/.agents --skill commit-sofer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/sofer/.agents/tree/main/skills/commit
Command: npx skills add https://github.com/sofer/.agents --skill commit-sofer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflows often suffer from inconsistent branching, unclear commit messages, and manual PR processes. This Skill provides guided commands and conventions to standardize feature branches, commits, PR creation, and merging using Conventional Commits.

Core Features & Use Cases

  • Create feature branches with consistent naming and base branch strategy.
  • Stage and commit changes using Conventional Commits formats.
  • Generate pull requests from the current branch and manage merges.
  • Default to standard commit behavior when no subcommand is provided.

Quick Start

Invoke the appropriate subcommand (branch, commit, pr, or merge) to manage your feature branches and pull requests in your repository.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git workflows with conventional commits for feature branching and pull requests?

You can automate git workflows by invoking subcommands for branch creation, commit staging, PR generation, and merging. This standardizes feature branch naming and applies Conventional Commits formats across your daily development process.

Does this git workflow automation support GitHub, GitLab, and Bitbucket for pull request creation?

Yes, the guided git workflow automation supports integrated PR processes across GitHub, GitLab, and Bitbucket. It manages pull request generation from your current feature branch and handles subsequent merge operations.

What is the best way to standardize commit messages and branch naming across a development team?

Standardizing commit messages and branch naming requires applying Conventional Commits formats and consistent base branch strategies. Guided subcommands enforce predictable branch creation and structured commit staging with guardrails.

How do I create a feature branch and generate a pull request using conventional commits?

Invoke the branch subcommand for consistent feature branch creation, stage changes using the commit subcommand for structured messages, then use the pr subcommand to generate a pull request from the current branch.

What happens if I run a git commit without specifying a subcommand?

When no subcommand is provided, the default behavior executes a standard git commit. The Skill applies conventional commit formats and ensures a clean working tree as a guardrail before staging changes.

When do I need conventional commits for managing feature branches and pull requests?

You need conventional commits when daily development workflows require predictable branch naming, structured commit messages, and integrated PR processes. This solves issues with inconsistent branching and manual pull request creation.