Does this skill run linting before committing?

Yes, it automatically detects and runs linting commands like pnpm lint or npm run lint to ensure code quality unless the --no-verify flag is used.

Can it help me follow the atomic commit principle?

Yes, the skill analyzes your diff to identify multiple distinct logical changes and will suggest breaking them into smaller, separate commits if necessary.

What commit message format does it use?

It follows the Conventional Commits specification (type: description) and prepends the appropriate Gitmoji based on the change type (e.g., ✨ for feat, 🐛 for fix).

How does it handle commits on the main branch?

If you are on the master or main branch, the skill will detect it and ask if you want to create a separate feature branch using a standardized naming convention before proceeding.

Conventional Git Commits

Name: Conventional Git Commits
Author: NeoLabHQ

byNeoLabHQ

•

542

•

Developer Tools

Automates the creation of standardized, emoji-enhanced conventional commit messages while managing branch workflows and code quality.

This Claude Code Skill streamlines the version control process by enforcing conventional commit standards and automating repetitive git tasks. It intelligently analyzes code diffs to suggest commit splits for better atomicity, runs pre-commit linting checks to ensure code quality, and handles branch protection by guiding users to create feature branches when working on protected branches like main or master. By integrating Gitmojis and structured formatting, it ensures a clean, readable, and professional commit history for any development project.

Key Features

01Automatic file staging for modified and new files when nothing is currently staged

02542 GitHub stars

03Integrated pre-commit linting support for pnpm, npm, yarn, and bun

04Intelligent diff analysis to suggest splitting large changes into atomic commits

05Automated conventional commit generation with context-aware Gitmojis

06Branch protection logic that enforces standardized naming for new feature branches

Use Cases

01Automating the transition from main branch development to feature-specific branches with correct naming

02Maintaining a clean and standardized commit history in professional team environments

03Ensuring code quality by running linting checks automatically before every commit to prevent CI failures

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add neolabhq/context-engineering-kit commit

For use in Claude.ai and ChatGPT

Download Skill