Commit Changes

Stage, format, and commit code changes with conventional commit messages.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rghsoftware/context-engine --skill commit-changes-rghsoftware
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Commit Changes
Source: https://github.com/rghsoftware/context-engine/tree/main/context-engine/skills/impl-commit
Command: npx skills add https://github.com/rghsoftware/context-engine --skill commit-changes-rghsoftware

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of staging, formatting, and committing code changes with conventional commit messages, ensuring code quality and consistency.

Core Features & Use Cases

  • Automated Code Formatting: Applies standard formatters based on the project's stack (Python, Vue/TypeScript, Rust, C/C++, Kotlin).
  • Conventional Commits: Generates commit messages following the conventional commit standard, including type, scope, description, and optional body.
  • Contextual Referencing: Allows referencing tasks (e.g., S001), features (e.g., NNN-FeatureName), and Architecture Decision Records (ADRs).
  • Use Case: After completing a set of coding tasks, you can use this Skill to automatically format your changes, create a descriptive commit message referencing the tasks completed, and then commit the changes.

Quick Start

Use the commit skill to stage and commit my current changes with the message "feat: Implement user authentication".

Frequently Asked Questions about Commit Changes

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

FAQPage Schema
How do I automatically stage and commit code changes with conventional commit messages?

To automatically stage and commit code changes, this Skill stages your files, applies standard formatters, and generates a conventional commit message. It ensures code quality and consistency by referencing tasks and ADRs directly in the commit history.

What is the best way to format code before creating a git commit?

The best way to format code before a git commit is using automated formatters. This Skill applies ruff, prettier, eslint, rustfmt, clang-format, or ktlint based on your project stack to ensure adherence to commit standards.

Does this automated commit tool support Python and TypeScript formatting?

Yes, this automated commit tool supports Python and TypeScript formatting. It applies ruff for Python and prettier or eslint for Vue and TypeScript projects to format code before staging and committing the changes.

Can I reference specific tasks or Architecture Decision Records in my conventional commits?

Yes, you can reference specific tasks or Architecture Decision Records in conventional commits. The Skill allows contextual referencing of tasks like S001, features like NNN-FeatureName, and ADRs directly within the generated commit message body.

Do I need specific formatters installed to use this conventional commit Skill?

Yes, you need specific formatters installed to use this conventional commit Skill. It requires Git and specific formatters like ruff, prettier, eslint, rustfmt, clang-format, and ktlint to be available in your environment to ensure code quality.