commit

Generate conventional commit messages from chat changes and apply them to the active Git branch.

27|2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/DataCovey/nornweave --skill commit-datacovey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/DataCovey/nornweave/tree/main/.cursor/skills/commit
Command: npx skills add https://github.com/DataCovey/nornweave --skill commit-datacovey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Committing chat-session changes to the active Git branch using conventional commits to enforce consistent history and clear intent.

Core Features & Use Cases

  • Generate conventional commit messages (feat, fix, docs, chore, etc.) from chat context based on changes made during a session.
  • Apply the commit to the current branch with an optional amend or squash workflow, enabling clean history and easier code reviews.
  • Integrate with existing CI and changelog workflows by producing standardized messages that align with semantic versioning.

Quick Start

Run the commit skill to generate and apply a conventional commit on your current branch.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commits from chat changes in a Git repository?

To generate conventional commits from chat changes, the Skill automates message creation based on your session context and applies it to the active Git branch. It requires a clean working tree to execute the commit workflow properly.

What is the best way to maintain a clean Git history across multiple file updates?

The best way to maintain clean Git history across multiple files is using conventional commit messages with amend or squash workflows. This approach enforces consistent history and clear intent for features, fixes, and documentation updates.

Do I need a clean working tree to apply chat-derived commits to my current branch?

Yes, you need a clean working tree in your Git repository context to apply chat-derived commits to the active branch. This ensures the automated conventional commit application integrates smoothly without conflicts.

Can I integrate semantic versioning with automated conventional commits for CI workflows?

Yes, you can integrate semantic versioning with CI workflows by producing standardized conventional commit messages. These messages align with changelog workflows to enforce consistent versioning history across development pipelines.

Does the commit Skill support squashing changes made during a chat session?

Yes, the commit Skill supports an optional squash workflow to apply commits to the current branch. This enables clean history and easier code reviews by combining multiple chat-derived changes into a single conventional commit.