commit

Draft and apply Conventional Commit messages from the staged diff via helper scripts.

Updated Sep 30, 2021

Search Tags:#automation #git #workflow #commit #scripts #conventional-commit

Ready to run

npx skills add https://github.com/isymchych/accel-os --skill commit-isymchych

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/isymchych/accel-os/tree/main/ai/codex/skills/commit-message
Command: npx skills add https://github.com/isymchych/accel-os --skill commit-isymchych

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Generate conventional commit messages from the helper-provided staged diff and apply them exclusively through the skill's helper scripts, avoiding direct git commands and enforcing consistency.

Core Features & Use Cases

Draft Conventional Commit messages from the staged changes and format them according to the Conventional Commits spec.
Retry path: reuse the most recent full commit message generated in this session.
Guardrails: all commits are created and applied via helper scripts to minimize user errors.

Quick Start

Say commit to trigger the workflow and have it draft and apply the commit message via the helper scripts.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate conventional commit messages automatically from staged changes?▼

This workflow drafts a conventional commit message directly from your staged git diff and applies it exclusively through helper scripts, ensuring consistent formatting without requiring direct git commands.

How can I commit using helper scripts without executing direct git commands?▼

You can commit without direct git commands by triggering the workflow with a simple commit request, which invokes the show_staged_diff.ts and commit_with_message.ts helper scripts to process and apply the changes securely.

What is the conventional commit format and when do I need it for my git workflow?▼

The conventional commit format standardizes commit messages using structured prefixes. You need it in your git workflow to enforce commit consistency, which helps automate changelog generation and semantic versioning.

Can I reuse a previous commit message if my staged changes fail to commit?▼

Yes, you can reuse a previous commit message. The workflow features a retry path that allows you to reuse the most recent full commit message generated in the current session for repeated attempts.

Does this commit automation workflow support retrying with the last generated message?▼

Yes, the commit automation workflow supports a retry path. If you need to attempt the commit again, it reuses the most recent full commit message generated during your active session to maintain consistency.