commit

Analyze git changes, stage relevant files, and generate Conventional Commits messages.

4|Updated Jan 9, 2026

Search Tags:#git #commit #staging #code-quality #version-control #conventional-commits

Ready to run

npx skills add https://github.com/baleen37/bstack --skill commit-baleen37

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the git commit process by guiding analysis, precise staging, and conventional-commit formatting to improve history quality.

Core Features & Use Cases

Guided analysis of changes to determine what should be included in a commit.
Selective staging with git add to avoid accidental inclusion of unrelated files.
Enforce Conventional Commits format and provide a ready-to-use template for commit messages.
Use case: when fixing a bug, you can create a single, well-scoped commit like fix(auth): correct login flow.

Quick Start

Identify the changes shown by git status, stage the required files with git add, and commit using a Conventional Commits style message.

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 for my git changes?▼

To write a conventional commit message, this Skill analyzes your git status and generates a scoped message like fix(auth): correct login flow. It stages only relevant files to ensure the commit history remains clean and well-structured.

What is the best way to stage only specific files for a git commit?▼

The best way to stage specific files is using selective git add to avoid accidental inclusion of unrelated changes. This Skill identifies relevant files and stages them individually before generating a single, well-scoped conventional commit.

How does this workflow prevent accidental secrets from being committed?▼

This workflow prevents accidental secrets by enforcing repository safety rules during the staging process. It carefully analyzes changes and selectively stages only relevant files, ensuring sensitive data is excluded from the final conventional commit.

Can I use this to create a single scoped commit for a bug fix?▼

Yes, you can use this to create a single scoped commit for a bug fix. It determines the appropriate commit scope from your changes and generates a conventional commit message like fix(auth): correct login flow for that specific fix.

Why should I selectively stage files instead of using git add all?▼

You should selectively stage files instead of using git add all to avoid mixing unrelated changes in a single commit. This approach analyzes your changes, stages only relevant files, and generates a focused conventional commit message to improve history quality.