commit

Name: commit
Availability: InStock
Author: tasky

Generate Conventional Commits messages with type, scope, and summary.

Updated Aug 23, 2026

Search Tags:#git #version control #development workflow #commit #conventional commits

Ready to run

npx skills add https://github.com/taskylizard/agents --skill commit-taskylizard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/taskylizard/agents/tree/main/skills/commit
Command: npx skills add https://github.com/taskylizard/agents --skill commit-taskylizard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating Git commits by enforcing the Conventional Commits standard, ensuring consistency and clarity in your project's history.

Core Features & Use Cases

Conventional Commits: Automatically formats commit messages with type, scope, and summary.
Guided Commit Creation: Helps users select appropriate types (feat, fix, etc.) and scopes.
Use Case: When you've finished a bug fix, use this skill to generate a commit message like fix(api): resolve authentication token expiration without needing to remember the exact format.

Quick Start

Use the commit skill to create a git commit with the type 'feat' and summary 'add user profile page'.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate Git commit messages following the Conventional Commits specification?▼

To generate Conventional Commits messages, this Skill formats your staged Git changes by enforcing structured types, scopes, and summaries. It utilizes the Git CLI to analyze status and diff outputs, producing a perfectly formatted commit message.

What is the Conventional Commits format for version control history?▼

The Conventional Commits format for version control structures messages into a type, an optional scope, and a summary. This standard solves inconsistent history issues by ensuring clarity, like generating `fix(api): resolve authentication token expiration` instead of unstructured text.

How do I commit specific staged files using a conventional commit workflow?▼

To commit specific staged files in a conventional commit workflow, you can provide user-specified file paths or globs. The process reads your Git status and diff for those targeted changes to automatically build the correctly formatted commit message.

Do I need Git CLI installed to create conventional commits?▼

Yes, you need the Git CLI installed to create conventional commits with this workflow. The process relies directly on Git CLI commands to read repository status, analyze code diffs, and execute the final commit operations on your staged changes.

Can I use this guided commit creation for development workflows without remembering commit types?▼

Yes, you can use guided commit creation for development workflows without remembering exact formats. It helps you select appropriate types like `feat` or `fix` and scopes, automatically building the final structured message from your summary input.