commit

Enforce non-interactive Git operations and Conventional Commits for commit messages.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures all Git operations, especially commits, adhere to best practices and avoid common pitfalls that can hang or disrupt automated workflows.

Core Features & Use Cases

  • Non-interactive Git Operations: Prevents Git commands from opening interactive editors, ensuring smooth execution.
  • Conventional Commits: Enforces a structured commit message format (<type>(<scope>): <summary>) for clarity and consistency.
  • Use Case: When making a bug fix, use this Skill to automatically stage all relevant files and generate a commit message like fix(api): resolve null pointer exception in user auth.

Quick Start

Commit all staged changes with the message "feat: implement user profile editing".

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce conventional commits in automated workflows?

To enforce conventional commits in automated workflows, this Skill structures Git messages into types, scopes, and summaries. It enforces non-interactive Git operations to prevent editor hangs and ensure smooth execution.

Why does my automated Git commit hang waiting for an editor?

Automated Git commit processes hang when commands trigger interactive text editors. This Skill prevents these hangs by enforcing non-interactive Git operations, ensuring structured commit messages are generated without user intervention.

How do I write a conventional commit message for a bug fix?

To write a conventional commit message for a bug fix, use the structured format of type, scope, and summary. This Skill manages commit bodies and scopes to generate messages like fix(api): resolve null pointer exception.

Can I specify exact file paths when staging changes for a commit?

You can specify exact file paths when staging changes by providing user instructions to the Skill. It handles these file paths for precise staging and committing, ensuring only targeted changes are included.

What is the correct format for conventional commit messages?

The correct format for conventional commit messages follows the pattern of type, scope, and summary. This Skill enforces this exact structure to maintain clarity and consistency across all Git version control actions.

How do I automate version control without manual editor input?

To automate version control without manual editor input, this Skill enforces non-interactive Git operations. It manages your commit messages and scopes automatically, preventing interactive editor prompts from disrupting workflow automation.