commit

Stage working tree changes and create Conventional Commits without pushing.

1|Updated Sep 17, 2025

Search Tags:#git #version control #commit #developer workflow #conventional commits #code governance

Ready to run

npx skills add https://github.com/mpazaryna/agentic-factory --skill commit-mpazaryna

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/mpazaryna/agentic-factory/tree/main/dev/developer-workflow/skills/commit
Command: npx skills add https://github.com/mpazaryna/agentic-factory --skill commit-mpazaryna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of staging changes and creating Git commits that adhere to the Conventional Commits specification, ensuring consistency and clarity in your project's history.

Core Features & Use Cases

Guided Staging: Ensures files are staged intentionally after review.
Conventional Commits: Enforces a standardized format for commit messages (type, scope, subject, body).
Git Governance: Implements best practices like avoiding git add ., never staging secrets, and not pushing by default.
Use Case: You've made several changes to a feature branch and want to commit them following project guidelines. This skill will guide you through reviewing, staging, and composing a well-formatted commit message.

Quick Start

Use the commit skill to stage your current working tree changes and create a Conventional Commit.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I create a git commit that follows conventional commits standards?▼

Staging changes intentionally and composing a structured message with type, scope, subject, and body creates a conventional commit. This process enforces Git governance rules to prevent staging unintended files or secrets.

What is the conventional commit format for version control history?▼

The conventional commit format standardizes version control history by structuring messages with a specific type, optional scope, subject, and body. This ensures consistency and clarity across project commits without automatically pushing changes.

How do I review and stage git diffs before committing?▼

Reviewing and staging git diffs involves inspecting working tree changes file by file and intentionally staging only the desired modifications. This guided staging approach avoids broad commands and prevents accidental inclusion of secrets.

Does this developer workflow commit process automatically push git changes?▼

No, this developer workflow commit process stages changes and creates a commit locally without pushing. Pushing is intentionally excluded by default to give you full control over when changes are published to the remote repository.

What are the git governance rules for staging files safely?▼

Git governance rules for staging files safely include avoiding broad staging commands, never staging secrets, and reviewing diffs before committing. These rules ensure only intended files are added to the working tree.