sl-commit

Generate Conventional Commits messages for Sapling SCM repositories.

484|76|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/flora131/atomic --skill sl-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sl-commit
Source: https://github.com/flora131/atomic/tree/main/.opencode/skills/sl-commit
Command: npx skills add https://github.com/flora131/atomic --skill sl-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of well-formatted commit messages adhering to the Conventional Commits specification, streamlining your version control workflow with Sapling SCM.

Core Features & Use Cases

  • Automated Commit Message Generation: Analyzes code changes and generates descriptive commit messages.
  • Conventional Commits Compliance: Ensures all commits follow the type: description format for better project history.
  • Change Analysis: Differentiates between logical changes to suggest breaking down large commits.
  • Use Case: After making several unrelated changes, use this Skill to automatically create separate, well-described commits for each logical change, maintaining a clean and understandable Git history.

Quick Start

Use the sl-commit skill to create a conventional commit for your current changes.

Frequently Asked Questions about sl-commit

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

FAQPage Schema
How do I generate conventional commits automatically with Sapling SCM?

To generate conventional commits with Sapling SCM, this Skill analyzes your repository status, adds untracked files, and diffs changes to automatically produce descriptive commit messages following the type: description format. It supports feat, fix, docs, style, refactor, perf, test, and chore commit types.

What is the conventional commits format for version control?

The conventional commits format structures version control messages as type: description, ensuring a clean and understandable project history. This Skill automates applying this specification to your Sapling SCM workflow by analyzing code changes to generate compliant messages.

Can I break down large commits into separate logical changes in Sapling?

Yes, you can break down large commits into separate logical changes in Sapling. This Skill differentiates between logical changes in your repository status and suggests creating separate, well-described commits for each change to maintain a clean project history.

Does this conventional commit tool work with Git repositories?

This conventional commit tool is designed for Sapling SCM, but Sapling operates as a source control manager that can work with Git. It analyzes your repository status and diffs changes to create well-formatted commit messages compliant with the conventional commits specification.

What's the best way to automate commit messages for multiple unrelated changes?

The best way to automate commit messages for multiple unrelated changes is using this Skill, which analyzes code changes and differentiates logical edits. It automatically creates separate, well-described conventional commits for each change, maintaining a clean and understandable version control history.