commit

Automate the Git commit-PR-merge workflow with branch creation and PR automation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stages, commits, PR creation, and merging to main are automated to enforce a consistent, auditable Git workflow across teams.

Core Features & Use Cases

  • Branch management: automatically creates a feature branch from the current state.
  • Descriptive commits: commits changes with meaningful messages when provided or inferred from staged changes.
  • PR automation: pushes to origin and opens a pull request with a concise summary and test plan.
  • Safe cleanup: merges to main and resets the working state, while excluding sensitive files.
  • Use Case: a developer finishing a bug fix can trigger this skill to push a branch, commit the fix with a message, and open a PR for review in one go.

Quick Start

Run this skill to automatically execute the standard Git commit-PR-merge cycle for your current repo.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate the git commit, PR, and merge workflow?

Automating the git commit, PR, and merge workflow involves guiding staging, branching, committing, pushing, and pull request creation in one go. This skill executes that cycle automatically while enforcing safeguards like excluding sensitive files.

What's the best way to ensure a clean git merge back to main?

Ensuring a clean git merge back to main requires resetting the working state after merging. This skill manages safe cleanup by merging to main and resetting your environment, while enforcing descriptive commit messages.

Can I automatically create a pull request with a test plan from staged changes?

Yes, you can automatically create a pull request with a concise summary and test plan from staged changes. This skill pushes your branch to origin and opens a pull request using messages inferred from your staged changes.

Does this git workflow automation exclude sensitive files during commits?

Yes, this git workflow automation excludes sensitive files during commits. It enforces safeguards throughout the staging, branching, and merging process to ensure sensitive files are not included in your pull requests.

How do I generate descriptive commit messages for bug fixes?

Generating descriptive commit messages for bug fixes is handled automatically by inferring context from staged changes. This skill commits your bug fixes with meaningful messages when they are not explicitly provided.

Do I need to manually create a feature branch before committing changes?

No, you do not need to manually create a feature branch before committing changes. This skill handles branch management by automatically creating a feature branch from your current state before staging and pushing.