skills.rest
sobhanashine
sobhanashineCOMMUNITY
Explore all skills by this author →
GitHub

commit-style

Generates Conventional Commit messages with type, scope, and subject.

1|Updated May 12, 2026
Search Tags:#git#code review#commit#conventional commits#commit history
One-click install
npx skills add https://github.com/sobhanashine/nazarato --skill commit-style-sobhanashine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-style
Source: https://github.com/sobhanashine/nazarato/tree/main/.agents/skills/commit-style
Command: npx skills add https://github.com/sobhanashine/nazarato --skill commit-style-sobhanashine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps maintain a clean and consistent commit history by enforcing the use of Conventional Commits with scope tags and issue links, making it easier to read and navigate your codebase's commit history.

Core Features & Use Cases

  • Enforce Conventional Commits: Prompts for required fields and formats in commit messages.
  • Scope Tags: Allows specifying the scope of the commit (e.g., auth, blog).
  • Issue Links: Integrates with issue tracking systems to reference linked issues.
  • Use Case: When writing a commit message or running git commit, this Skill ensures that the message follows a standard format, which improves the readability and maintainability of the commit history.

Quick Start

Use the commit-style skill to generate a commit message for your new feature in the 'auth' module.

Frequently Asked Questions about commit-style

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

FAQPage Schema
How do I generate conventional commit messages for git?▼

To generate conventional commit messages for git, this Skill structures your commit with a required type, scope, and subject. It ensures your version control history follows a standard format, improving overall readability and maintainability.

What is the best way to maintain a clean git commit history?▼

Maintaining a clean git commit history is achieved by enforcing conventional commits with mandatory scope tags and issue links. This standard format makes it easier to read and navigate your codebase's historical changes.

Can I include issue tracking links in my conventional commits?▼

Yes, you can include issue tracking links in your conventional commits. This Skill integrates with issue tracking systems to reference linked issues, ensuring that your commit messages connect directly to relevant tracking tickets.

How do I add a scope tag like auth to a git commit message?▼

To add a scope tag like auth to a git commit message, this Skill prompts you for the required fields and formats the message accordingly. Specifying the scope helps categorize changes within specific modules of your software development project.

Do I need any external dependencies to enforce conventional commits?▼

No external dependencies are required to enforce conventional commits with this Skill. It operates independently to prompt for required fields and format your commit messages, ensuring a standard structure without needing additional software.

Related Skills

Explore More Software Engineering Skills→
PL-Coding-GmbHPL-Coding-GmbH
6

git-commit

Commit uncommitted git changes as atomic Conventional Commits.

Official
Intermediate
ctrsploitctrsploit
153

commit-message

Generate semantic Git commit messages from staged changes using Conventional Commits.

Official
Intermediate
PaulRBergPaulRBerg
82

Markdown Docs

Update Markdown documentation to match current codebase structure.

Community
Advanced
BobJu0721BobJu0721

commit

Enforce Conventional Commits, branch naming, and PR guidelines for Git workflows.

Community
Advanced