commit

Name: commit
Availability: InStock
Author: papeete-consulting-lab

Create and publish conventional git commits with validated changes.

Updated Apr 24, 2026

Search Tags:#git #pull request #commit #conventional commits #github #code workflow

Ready to run

npx skills add https://github.com/papeete-consulting-lab/banking-reliever --skill commit-papeete-consulting-lab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/papeete-consulting-lab/banking-reliever/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/papeete-consulting-lab/banking-reliever --skill commit-papeete-consulting-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the risk and friction from creating professional git commits by automating validation, staging, commit message generation, and publishing workflows while protecting sensitive files.

Core Features & Use Cases

Safe Commit Preparation: Detects sensitive files, reviews changes, runs appropriate tests, and stages files explicitly instead of using unsafe bulk staging commands.
Conventional Commit Automation: Generates standardized commit messages, evaluates version impact, handles breaking changes, and includes required attribution metadata.
Publishing Workflow Support: Commits changes, pushes branches safely, and optionally creates GitHub pull requests for completed work.

Quick Start

Use the commit skill to review my changes, create a conventional commit, and push it to the remote repository.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automate conventional commit generation for git changes?▼

Automating conventional commit generation for git changes requires reviewing staged files, evaluating version impact, and generating standardized messages with required attribution metadata. This workflow detects breaking changes and formats commit messages automatically to maintain consistent project history.

What's the best way to prevent sensitive files from being committed to GitHub?▼

Preventing sensitive files from being committed to GitHub requires secure file filtering and explicit staging instead of unsafe bulk staging commands. The workflow detects sensitive files during commit preparation, reviews changes, and stages files individually to ensure controlled git operations.

Can I automatically create a pull request after pushing a git branch?▼

Creating a pull request after pushing a git branch is supported through publishing workflow automation. After committing changes and safely pushing branches to the remote repository, the workflow optionally creates GitHub pull requests for completed work to streamline code review.

How does test execution handling work during automated git workflows?▼

Test execution handling during automated git workflows runs appropriate tests as part of safe commit preparation. The process validates testing before staging files explicitly, ensuring code changes pass validation before conventional commit generation and branch publishing occur.

Do I need to manually stage files before generating a conventional commit?▼

Manual file staging is unnecessary before generating a conventional commit because the workflow handles explicit staging automatically. Instead of unsafe bulk staging commands, the process reviews changes, detects sensitive files, and stages files explicitly to maintain controlled git operations.

When should I avoid automated git commit workflows for code changes?▼

Automated git commit workflows should be avoided when you need manual control over staging individual files or when custom commit message formats are required. The workflow enforces conventional commits and explicit staging, which may not suit projects with non-standard version impact analysis requirements.