commit

Generate and validate conventional commit messages for Rust workspaces with crate-based scope rules.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/edgeandnode/ampup --skill commit-edgeandnode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/edgeandnode/ampup/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/edgeandnode/ampup --skill commit-edgeandnode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate and validate conventional commit messages for Rust workspaces with crate-based scope rules to ensure consistency across multiple crates.

Core Features & Use Cases

  • Enforces the conventional commits format (type(scope): description) and ensures the scope matches the affected crates in the workspace.
  • Validates that the scope and description align with the changeset entries and review process.
  • Assists with amend workflows by regenerating or verifying the prior commit message to maintain accuracy.

Quick Start

Describe a change and let the tool output a properly formatted commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for a Rust workspace?

To generate conventional commit messages for a Rust workspace, describe your change and the tool outputs a properly formatted message. It enforces the type(scope): description format and ensures the scope matches the affected crates in your workspace.

How do I validate that a git commit scope matches the affected crates?

Validating a git commit scope matches affected crates is handled by checking the scope and description against your changeset entries. This ensures the conventional commit scoping rules align accurately with the actual code modifications.

Can I use this tool to amend a commit message across a multi-crate project?

Yes, you can amend a commit message across a multi-crate project. It assists with amend workflows by regenerating or verifying the prior commit message to maintain accuracy with your workspace changes.

What is the conventional commits format for workspace scoping?

The conventional commits format for workspace scoping requires a type(scope): description structure. It enforces crate-based scope rules to ensure consistency across multiple crates within a Rust workspace.

Does this tool enforce crate-based scoping rules for Rust workspace commits?

Yes, this tool enforces crate-based scoping rules for Rust workspace commits. It validates that the scope matches the affected crates and ensures the description aligns with the changeset entries and review process.

Why do my conventional commit messages fail validation in a multi-crate project?

Conventional commit messages fail validation in a multi-crate project when the scope and description do not align with the changeset entries. The tool verifies message accuracy against the changeset to prevent inconsistent workspace commits.