commit

Automate Git staging, committing, pushing, and pull request creation.

1|Updated Mar 11, 2025
One-click install
npx skills add https://github.com/danielstewart77/hive_mind --skill commit-danielstewart77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/danielstewart77/hive_mind/tree/main/specs/skills/commit
Command: npx skills add https://github.com/danielstewart77/hive_mind --skill commit-danielstewart77

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the Git workflow by automating the process of staging changes, committing them with a message, pushing to a remote repository, and creating a pull request, while ensuring adherence to branch protection rules.

Core Features & Use Cases

  • Automated Git Operations: Handles staging, committing, and pushing code changes.
  • Branch Management: Automatically creates feature branches when on the master branch.
  • Pull Request Creation: Generates a pull request with a pre-defined template.
  • Use Case: After making several code modifications for a new feature, you can use this Skill to quickly commit and push your changes and open a PR for review without manually executing multiple Git commands.

Quick Start

Use the commit skill to stage all changes, commit them with the message "feat: implement user authentication", and push to a new feature branch.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git staging, committing, and pushing to a remote branch?

Automating git staging, committing, and pushing is handled by executing a single command that stages all changes, formats the commit message, and pushes to a remote feature branch. This streamlines the entire Git workflow without manual commands.

How does branch protection work when committing directly to the master branch?

Branch protection during a commit is handled by automatically creating a new feature branch when you are on the master branch. This ensures you never push directly to master and maintains proper code integration workflows.

What is the best way to create a pull request with a pre-defined template after committing code?

Creating a pull request with a pre-defined template is done automatically after your code is committed and pushed. The workflow generates the PR for review, ensuring proper formatting and co-authorship details are included.

Can I include co-authorship information in my automated commit messages?

Yes, co-authorship information is included in automated commit messages. The process ensures proper commit message formatting with co-authorship details, facilitating efficient code review and clear authorship tracking.

What do I need to set up before using an automated Git workflow for pull requests?

Before using an automated Git workflow for pull requests, you need a Git repository with a remote configured and branch protection rules established. The environment requires Git installed to handle staging, pushing, and PR creation.

Why does my automated pull request creation fail on a protected branch?

Automated pull request creation fails on a protected branch if you attempt to push directly to master without creating a feature branch. The workflow handles this by automatically creating a feature branch to bypass branch protection rules.