Commit Changes

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.

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.

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.

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.

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.

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.