commit

Stage changes, commit, create a pull request, and merge to main.

2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/clearsmog/claude-skills --skill commit-clearsmog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/clearsmog/claude-skills/tree/main/commit
Command: npx skills add https://github.com/clearsmog/claude-skills --skill commit-clearsmog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes the commit-PR-merge workflow to reduce manual errors during software delivery.

Core Features & Use Cases

  • Stage changes safely, excluding secrets from staging.
  • Create a branch, push, and open a PR, then merge to main.
  • Use in collaborative development to enforce consistent commit messages and PR reviews.

Quick Start

Invoke the commit skill to automatically stage changes, commit with a descriptive message, push a PR, and merge into main.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate a git workflow to stage, commit, and merge a pull request?

You can automate the git workflow by orchestrating staging, committing with a message, pushing a PR, and merging to main. This standardizes feature branch operations, code reviews, and CI integration to reduce manual errors.

What is the best way to exclude secrets when staging changes for a commit?

To exclude secrets when staging changes, use a workflow that safely identifies and prevents sensitive data from being added to the staging area. This ensures sensitive files are not accidentally committed during the branch creation process.

Does the automated commit and PR workflow work with the gh CLI for pull requests?

Yes, the automated commit and PR workflow uses the gh CLI for pull request operations. It integrates with collaborative software development workflows to safely create branches, push commits, open PRs, and merge into main.

How do I create a branch and open a pull request for collaborative development?

To create a branch and open a pull request, you stage changes, commit with a descriptive message, and use PR operations via gh CLI. This enforces consistent commit messages and PR reviews in collaborative development.

Can I enforce consistent commit messages and PR reviews using an automated workflow?

Yes, you can enforce consistent commit messages and PR reviews using an automated workflow. By standardizing the commit-PR-merge process, it reduces manual errors and ensures safe branching during software delivery.