commit

Generate Sun Lab style-compliant git commit messages from local code changes.

3|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Sun-Lab-NBB/ataraxis --skill commit-sun-lab-nbb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Sun-Lab-NBB/ataraxis/tree/main/plugins/automation/skills/commit
Command: npx skills add https://github.com/Sun-Lab-NBB/ataraxis --skill commit-sun-lab-nbb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create clear, concise, and style-compliant git commit messages, ensuring your project history is easy to understand and maintain.

Core Features & Use Cases

  • Analyzes Local Changes: Reviews staged, unstaged, and untracked files to understand modifications.
  • Drafts Style-Compliant Messages: Generates messages following Sun Lab conventions for header length, verb tense, and content focus.
  • Use Case: After making several code changes to fix a bug, you can invoke this skill to get a perfectly formatted commit message ready to be used.

Quick Start

Draft a commit message for my recent code changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a git commit message from my local code changes?

This skill generates git commit messages by analyzing your local code changes across staged, unstaged, and untracked files to accurately reflect the 'what' and 'why' of your modifications.

What is the proper format for a professional git commit message?

A professional git commit message adheres to style rules governing header length, verb tense, and content focus, ensuring project history remains clear, concise, and easy to maintain.

Can I automatically draft version control messages for untracked files?

Yes, you can draft version control messages for untracked files because the skill reviews staged, unstaged, and untracked files together to understand all local modifications before generating the message.

Does the generated commit message include tool attribution or authorship details?

No, the generated commit message excludes tool attribution and authorship details, ensuring the content focuses strictly on the technical modifications and the reasoning behind the code changes.

What is the best way to ensure my commit messages follow team code review conventions?

The best way to ensure commit messages follow code review conventions is to generate them via this skill, which drafts text compliant with Sun Lab rules for header length, verb tense, and content focus.