commit

Stage and commit Git changes with conventional commit guidance.

41|15|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/foyzulkarim/skills --skill commit-foyzulkarim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/foyzulkarim/skills/tree/main/dev-pipeline/skills/commit
Command: npx skills add https://github.com/foyzulkarim/skills --skill commit-foyzulkarim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures git commits are staged, titled, and executed with confidence by guiding developers through diff inspection, sensitive file awareness, and conventional messaging before finalizing a commit.

Core Features & Use Cases

  • Phased Staging Intelligence: Runs git status and git diff --stat, reports staged versus unstaged files, flags sensitive filenames, and prompts for precise staging commands.
  • Conventional Commit Drafting: Infers the dominant commit type from the diff, extracts task numbers from the branch, and composes compliant headers with concise descriptions.
  • Confirmed Execution Workflow: Allows edits or cancellation, enforces hooks, and only commits after explicit confirmation, making it ideal for finalizing work at any pipeline stage.

Quick Start

Ask the commit skill to stage your desired files and draft a conventional commit message based on the current diff before you confirm.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a conventional commit message from a git diff?

To write a conventional commit message from a git diff, the Skill inspects staged files, infers the dominant commit type from the changes, and drafts a compliant header with a concise description.

What is the best way to stage specific files and avoid committing sensitive data in git?

Staging files safely requires running git status and diff checks to separate staged versus unstaged files, which this process handles by flagging sensitive filenames and prompting for precise staging commands.

How do I extract task numbers from a git branch for a commit title?

Extracting task numbers from a git branch for a commit title is handled through task number heuristics, where the branch name is analyzed to automatically pull identifiers into the conventional commit header.

Can I review and edit a conventional commit message before executing git commit?

Yes, you can review and edit a conventional commit message before execution, as the workflow allows edits or cancellation and only commits after explicit confirmation without skipping git hooks.

Does the git commit workflow enforce hooks when finalizing changes?

Yes, the git commit workflow enforces hooks when finalizing changes, ensuring that all configured git hooks run successfully during the confirmed execution phase before the commit is completed.