skills.rest
gitkraken
gitkrakenOFFICIAL
Explore all skills by this author →
Website𝕏@gitkrakenGitHub

commit

Generate conventional Git commits with guided status checks and diff reviews.

9.9k|1.8k|Updated Aug 8, 2016
Search Tags:#git#code review#version control#development workflow#commit#git conventions
One-click install
npx skills add https://github.com/gitkraken/vscode-gitlens --skill commit-gitkraken
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/gitkraken/vscode-gitlens/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/gitkraken/vscode-gitlens --skill commit-gitkraken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create well-formatted and conventional Git commits, ensuring clarity and consistency in your project's history.

Core Features & Use Cases

  • Standardized Commit Messages: Enforces a specific format for commit messages (third-person singular present tense, line length limits, issue referencing).
  • Guided Workflow: Provides a step-by-step process for preparing and making commits, including status checks, diff reviews, and staging.
  • Use Case: When you've made several changes and need to commit them, this Skill will guide you through reviewing your work, drafting an appropriate message, and executing the commit safely.

Quick Start

Use the commit skill to create a git commit with the message 'Adds feature X and fixes bug Y'.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a well-formatted Git commit message that follows conventions?▼

A well-formatted Git commit uses third-person singular present tense, enforces line length limits, and includes issue referencing to maintain project history clarity and consistency.

What is the best way to safely stage and review code changes before committing?▼

The best way to commit safely is following a guided workflow: run status checks, review diffs, stage changes properly, and execute the commit without dangerous flags like --force or --no-verify.

How do I generate a Git commit message for multiple types of changes?▼

To generate a Git commit for multiple changes, draft a message summarizing the additions and fixes, ensuring it adheres to specific conventions like third-person present tense and proper issue referencing.

Why should I avoid using --force or --no-verify when creating Git commits?▼

You should avoid --force and --no-verify when creating Git commits to ensure standardized practices and prevent bypassing essential status checks, diff reviews, and repository safety validations.

Does this guided Git commit workflow require any external dependencies?▼

No, this guided Git commit workflow requires no external dependencies, allowing you to directly enforce message structure, review diffs, and stage changes safely within your development environment.

Related Skills

Explore More Software Engineering Skills→
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
a-taka-tak
1

git-commit-push

Automates staging, committing, and pushing with standardized Git workflow.

Community
Basic
ksopylaksopyla

git-workflow

Enforce Git workflow conventions for branch naming, commit messages, and pull requests.

Community
Intermediate
fiftynotaififtynotai
10

release

Generate changelogs and semantic version bumps from git commit history.

Community
Intermediate