skills.rest
brave-experiments
brave-experimentsOFFICIAL
Explore all skills by this author →
GitHub

commit

Create atomic Git commits with descriptive messages and optional branch creation.

4|Updated Feb 2, 2026
Search Tags:#git#development#version control#commit#branching#code
One-click install
npx skills add https://github.com/brave-experiments/brave-core-bot --skill commit-brave-experiments
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/brave-experiments/brave-core-bot/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/brave-experiments/brave-core-bot --skill commit-brave-experiments

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating clean, logical Git commits, ensuring your commit history is organized and easy to understand without unnecessary attribution lines.

Core Features & Use Cases

  • Atomic Commits: Creates commits that represent single, logical units of work.
  • Branching: Option to create a new descriptive branch before committing.
  • Pushing: Option to push commits to the remote repository after successful commits.
  • Fixup Commits: Supports using fixup commits for unpushed changes and squashing them via rebase.
  • Use Case: You've made several unrelated changes. Use this Skill to create separate, well-described commits for each logical change (e.g., one for a bug fix, another for a small refactor) and then push them.

Quick Start

Commit the current staged changes on the current branch and push them to the remote.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create atomic Git commits with descriptive messages?▼

Atomic Git commits are created by grouping individual logical units of work into separate commits with descriptive messages. This automates the process, ensuring your commit history remains clean and organized without unnecessary attribution lines.

Can I create a new branch and push Git commits to a remote repository at the same time?▼

Yes, you can create a new descriptive Git branch and push commits to a remote repository. Options include branching before committing and pushing immediately after successful commits to streamline code contribution workflows.

What is the best way to squash unpushed changes using fixup commits?▼

The best way to squash unpushed changes is by using fixup commits followed by non-interactive rebasing. This maintains a clean commit history by combining related adjustments before pushing to the remote.

How do I split unrelated code changes into separate Git commits?▼

Unrelated code changes are split into separate Git commits by creating atomic commits for each logical change. You generate one commit for a bug fix and another for a refactor to keep history logical.

Related Skills

Explore More Software Engineering Skills→
htlin222htlin222
77

git_status

Display modified, added, and deleted files in a Git repository.

Community
Basic
dtbuchholzdtbuchholz

commit-push-pr

Stage Git changes, create conventional commits, push branches, and open pull requests via GitHub CLI.

Community
Intermediate
softsparksoftspark
161

commit

Generate Conventional Commits and validate staged git changes for secrets and large files.

Community
Intermediate
sasamukusasamuku
8

fixup-commit

Create fixup commits and run autosquash rebase on a target branch.

Community
Basic