Creates commits strictly following Conventional Commits format. ALWAYS read BEFORE committing changes, amending commits, or when the user mentions git commits, conventional commits, or commit messages.

Create well-formatted git commits with conventional commit format and emoji. Automatically runs pre-commit checks (lint, build, docs), analyzes changes, suggests splitting when appropriate, and...

Coding patterns and best practices for OneKey development. Use when writing React components, handling promises, error handling, or following code conventions. Triggers on react, component, hooks,...

Generate semantic commit messages following conventional commits format. Use when committing code, staging changes, writing commit messages, requesting git commit, or when user mentions commit,...

Conventional Commits with quality checks

Expert in Ruby and Rails development with conventions and best practices

Generate CHANGELOG entries following conventional commits format with

Suggest better variable, function, and class names based on context and conventions.

Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase

Write consistent high-quality Git commits following project conventions

Development patterns for Obsidian. Load when implementing features or following coding conventions.

Advanced Git workflows, branching strategies, and commit conventions

Branch strategy, commit conventions, merge conflict resolution and Git best practices guide.

Branch stratejisi, commit conventions, merge conflict çözümü ve Git best practices rehberi.

Conventional Commits specification. Covers commit structure, types, breaking changes. Keywords: feat, fix, BREAKING CHANGE.

Implement semantic versioning (SemVer) with automated release management. Use conventional commits, semantic-release, and version bumping strategies.

Automated code review against project conventions (CLAUDE.md) and best practices

Draft a conventional commit message when the user asks for help writing a commit message.

Enforce consistent React component naming conventions using domain + role patterns. Use when creating, reviewing, or refactoring components.

Manage Git commits using conventional commit format with atomic staging. Use when committing changes, staging files, or creating commit messages.