المهارات Git Commit Helper
📝

Git Commit Helper

آمن

Generate commit messages from git diffs

Writing clear commit messages takes time and consistency. This skill provides structured guidance, conventional commit formats, and templates to generate descriptive commit messages automatically based on staged changes.

يدعم: Claude Codex Code(CC)
⚠️ 67 ضعيف
1

تنزيل ZIP المهارة

2

رفع في Claude

اذهب إلى Settings → Capabilities → Skills → Upload skill

3

فعّل وابدأ الاستخدام

اختبرها

استخدام "Git Commit Helper". Generate a commit message for these staged changes that add user login functionality

النتيجة المتوقعة:

  • feat(auth): add user login with email and password
  •  
  • Implement user authentication with:
  • - Email and password validation
  • - Session token generation
  • - Login endpoint handler
  •  
  • 🤖 Generated with Claude Code
  • Co-Authored-By: Claude <noreply@anthropic.com>

التدقيق الأمني

آمن
v3 • 1/10/2026

Pure prompt-based skill containing only markdown documentation. No executable code, network calls, file system access, or external commands. Contains commit message templates and best practices guidance only.

2
الملفات التي تم فحصها
358
الأسطر التي تم تحليلها
0
النتائج
3
إجمالي عمليات التدقيق
لا توجد مشكلات أمنية
تم تدقيقه بواسطة: claude عرض سجل التدقيق →

درجة الجودة

41
الهندسة المعمارية
100
قابلية الصيانة
81
المحتوى
22
المجتمع
100
الأمان
70
الامتثال للمواصفات

ماذا يمكنك بناءه

Write clear commit messages

Generate consistent, descriptive commit messages following industry standards for personal projects.

Maintain commit history

Create standardized commit messages across team repositories for better changelog generation.

Document changes properly

Write professional commit messages that help contributors understand changes and automate releases.

جرّب هذه الموجهات

Basic commit help 
Help me write a commit message for my staged changes. Here is the git diff output:
Conventional format 
Write a conventional commit message for these staged changes using feat, fix, or other appropriate types:
Breaking changes 
Generate a commit message that indicates a breaking change in the API for these staged changes:
Multi-file commits 
Write a comprehensive commit message for these multiple related file changes, grouping them logically:

أفضل الممارسات

  • Use imperative mood for descriptions (add, not added; fix, not fixed)
  • Keep the subject line under 50-72 characters
  • Explain WHY the change was made, not just WHAT changed
  • Reference related issues using Closes # or Fixes # tokens

تجنب

  • Using vague messages like update, fix stuff, or changes
  • Including implementation details in the summary line
  • Using past tense (fixed, added instead of fix, add)
  • Writing long paragraphs in the subject line without body separation

الأسئلة المتكررة

What commit types are supported?
feat, fix, docs, style, refactor, test, chore, perf, build, ci, and revert. Each maps to specific semantic versioning impacts.
What is the maximum length for commit messages?
Subject lines should be under 72 characters. Body paragraphs can be longer but stay concise.
Does this integrate with Git hosting platforms?
No. This skill generates message text. You apply the message when running git commit manually.
Is my repository data safe?
Yes. The skill only processes git diff text you provide. No repository data is stored or transmitted.
Why are my commit messages not working?
Ensure you provide the full git diff --staged output. The skill needs to see what actually changed to generate accurate messages.
How is this different from commit templates?
This skill actively analyzes your changes and generates appropriate messages. Commit templates only provide formats you fill manually.

تفاصيل المطور

المؤلف

Joseph OBrien

الترخيص

MIT

المستودع

https://github.com/89jobrien/steve/tree/main/steve/skills/git-commit-helper

مرجع

main

بنية الملفات

📁 references/

📄 git-commit.template.md

📄 SKILL.md