commit

Guide users through creating Conventional Commits with structured messages.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/AvatarGanymede/pcraft --skill commit-avatarganymede
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/AvatarGanymede/pcraft/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/AvatarGanymede/pcraft --skill commit-avatarganymede

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Skill solves the issue of creating consistent and conventional Git commits. It assists users in maintaining clean and understandable commit history.

Core Features & Use Cases

  • Conventional Commit Format: Enforces a clear commit message format for ease of release notes and change tracking.
  • Automated Checks: Pre-commit hooks for code quality, formatting, and linting before committing.
  • Multi-Step Process: Guided steps for ensuring all necessary checks are performed before finalizing a commit.

Quick Start

Stage and commit changes by saying, "commit my changes with a description following Conventional Commits."

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional commits with a structured git commit message?

To create conventional commits, this Skill guides you through staging files and structuring your git commit message to ensure clean history and easier release notes tracking. It walks both new and experienced users through the committing workflow.

What is the conventional commit format and why use it for git committing?

The conventional commit format enforces a clear, structured git commit message syntax for easier release notes and change tracking. You use it to maintain a clean, understandable commit history across your software engineering projects.

Can I run pre-commit hooks for code quality and linting before committing changes?

Yes, you can run pre-commit hooks for code quality, formatting, and linting before committing. The Skill includes multi-step automated checks to verify all pre-commit validations are completed before finalizing your conventional commit.

Does this conventional commit workflow support users unfamiliar with git?

Yes, this conventional commit workflow supports users unfamiliar with git by providing guided multi-step instructions. It caters to both new users and those familiar with git, ensuring proper file staging and pre-commit checks before committing.

What is the best way to automate release notes generation from git commits?

The best way to automate release notes generation is by enforcing a conventional commit format during git committing. This ensures a consistent, structured commit history that can be easily parsed for tracking changes and generating release documentation.