commit

Automate Git commits with branch protection, rebasing, and conventional messages.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of committing code changes, ensuring consistency, safety, and adherence to best practices like Conventional Commits.

Core Features & Use Cases

  • Branch Protection: Automatically creates feature branches for protected branches (main, develop, etc.).
  • Rebase Workflow: Rebases onto the base branch to maintain a clean, linear history.
  • Smart Staging: Intelligently stages files, excluding secrets and generated artifacts.
  • Conventional Commits: Generates commit messages following the Conventional Commits standard.
  • Push Confirmation: Offers to push changes after a successful commit.

Quick Start

Use the commit skill to save my work and push the changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commit messages to follow conventional commits?

Automating git commit messages with conventional commits is handled by generating standardized messages automatically during the staging process. This ensures consistent commit history formatting without manual input, enforcing best practices across your codebase.

Can I rebase onto the base branch automatically before committing changes?

Yes, rebasing onto the base branch is performed automatically before committing changes. This rebase workflow maintains a clean, linear git history by integrating the latest updates from your base branch seamlessly into your current feature branch.

How do I prevent accidental commits to the main or develop branches?

Preventing accidental commits to main or develop branches is achieved through branch protection rules. The system automatically detects protected branches like main, develop, and release, and creates a new feature branch before staging any changes.

Does smart staging exclude secrets and sensitive information from git commits?

Smart staging intelligently excludes secrets and sensitive information from your git commits. During the staging process, it automatically filters out sensitive files and generated artifacts, ensuring only safe, relevant code changes are included in the final commit.

What is the best way to push git commits to origin after staging?

The best way to push git commits to origin is using the integrated push confirmation feature. After successfully completing a commit, the workflow offers to automatically push your changes to the origin remote, streamlining the entire code synchronization process.