Commit Changes

Stage, format, and commit changes with conventional commit messages referencing ADRs.

Updated Aug 27, 2026

Search Tags:#git #commit #adr #version-control #code-formatting #conventional-commits

Ready to run

npx skills add https://github.com/rghamilton3/mission-control-rack --skill commit-changes-rghamilton3

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Commit Changes
Source: https://github.com/rghamilton3/mission-control-rack/tree/main/.claude/skills/impl-commit
Command: npx skills add https://github.com/rghamilton3/mission-control-rack --skill commit-changes-rghamilton3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Staging, formatting, and committing changes with conventional commit messages that reference feature context and ADRs to ensure traceable development history.

Core Features & Use Cases

Review changes to map them to related features and ADR decisions.
Automatically format code for the target stack (e.g., Python with ruff, JavaScript with prettier/eslint, Rust with rustfmt) before committing.
Assemble and enforce conventional commit messages that include Tasks, Feature references, and ADR identifiers.

Quick Start

Tell me to commit the latest task changes using a conventional message like feat(auth): implement login and reference ADR-001.

Frequently Asked Questions about Commit Changes

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

FAQPage Schema

How do I create conventional commit messages with ADR references and feature context?▼

To create conventional commit messages, this Skill enforces required fields like Tasks and Feature references while embedding ADR identifiers. It reviews your changes, maps them to related features, and assembles a traceable commit message for your development history.

How do I format code automatically before staging and committing changes in git?▼

To format code before committing, this Skill applies appropriate formatters for your target stack, such as ruff for Python, prettier/eslint for JavaScript, and rustfmt for Rust. It prevents committing changes without proper formatting to maintain code quality.

What is the best way to enforce required fields in conventional commit messages?▼

Enforcing required fields in conventional commit messages is handled by this Skill during the assembly process. It ensures that Task references, Feature context, and ADR identifiers are included before allowing the commit, preventing incomplete or untraceable history entries.

Does this git commit workflow support multiple tasks and different code formatting stacks?▼

Yes, this git commit workflow supports committing multiple tasks and applying stack-specific code formatting. It automatically detects your stack to run the correct formatter and can process multiple task changes within a single conventional commit message.

Why does my commit fail or get blocked without proper code formatting?▼

Your commit fails without proper code formatting because this Skill actively prevents committing unformatted code. It enforces formatting rules for your specific stack before staging to ensure that only clean, properly formatted changes are committed to the repository.

When do I need to reference ADR decisions in my conventional commit messages?▼

You need to reference ADR decisions in conventional commit messages when mapping changes to architectural decisions. This Skill reviews your changes and automatically embeds ADR references when applicable, ensuring traceable development history and clear feature context.