git-commit — community git-commit, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for Version Control Agents needing precise Git workflow management and commit message drafting. Commit changes (git commit) for this repo and write consistent commit messages (type(scope) prefix, impact/risk, what/why/how, testing summary, follow-ups, references).

semanticdreams semanticdreams
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
39
Canonical Locale
en
Detected Body Locale
en

Perfect for Version Control Agents needing precise Git workflow management and commit message drafting. Commit changes (git commit) for this repo and write consistent commit messages (type(scope) prefix, impact/risk, what/why/how, testing summary, follow-ups, references).

Core Value

Empowers agents to verify change sets and stage code safely using Git commands like `git status`, `git diff`, and `git add -p`, while avoiding secret exposure through `git diff --staged` and regular expression filtering with `rg`.

Ideal Agent Persona

Perfect for Version Control Agents needing precise Git workflow management and commit message drafting.

↓ Capabilities Granted for git-commit

Verifying change sets before committing
Drafting informative commit messages
Staging code selectively with `git add -p`

! Prerequisites & Limits

  • Requires Git repository access
  • Needs careful handling of sensitive information like API keys and credentials

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is git-commit?

Perfect for Version Control Agents needing precise Git workflow management and commit message drafting. Commit changes (git commit) for this repo and write consistent commit messages (type(scope) prefix, impact/risk, what/why/how, testing summary, follow-ups, references).

How do I install git-commit?

Run the command: npx killer-skills add semanticdreams/space/git-commit. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for git-commit?

Key use cases include: Verifying change sets before committing, Drafting informative commit messages, Staging code selectively with `git add -p`.

Which IDEs are compatible with git-commit?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for git-commit?

Requires Git repository access. Needs careful handling of sensitive information like API keys and credentials.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add semanticdreams/space/git-commit. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use git-commit immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

git-commit

Install git-commit, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Git Commit Messages (space)

Use this skill whenever you're about to create a commit (or when asked to "commit", "write a commit message", "draft a commit", etc.).

Workflow and safety

  • Verify the change set:
    • git status
    • git diff
    • git diff --staged
  • Stage only what you intend to ship; prefer git add -p for mixed diffs.
  • Never commit secrets/credentials. When in doubt:
    • git diff --staged | rg -n -i "api[_-]?key|secret|token|password|-----begin|private key"
  • Avoid destructive history ops unless explicitly asked (reset --hard, clean -fdx, rebase, --amend, force-push).

Commit subject line

  • Format: type(scope): <imperative subject> (scope optional).
  • Keep it <= 72 chars and in imperative mood ("Add", "Fix", "Refactor").
  • Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert.
  • Scopes (when useful): engine, render, physics, audio, lua, ui, assets, scripts.
  • Breaking changes: append an exclamation mark after type/scope (e.g. feat!:) and call it out in Impact + Risk.

Body (required for non-trivial changes)

Be explicit about impact (user-visible) vs what changed (code/data). Include risk when plausible.

Template:

type(scope): Short imperative subject (<= 72 chars)

Impact:
- <user-visible result / behavior change; include repro if useful>

What:
- <key code/data changes>

Why:
- <motivation / constraints>

How:
- <implementation approach, key files/systems>

Risk:
- <what could go wrong + mitigations/rollback>

Testing:
- <commands run + brief summary; DO NOT paste full logs>

Follow-ups:
- <next steps / cleanup / tech debt>

References:
- Refs: #123

Testing section expectations

  • Prefer running the full suite before committing:
    • SKIP_KEYRING_TESTS=1 XDG_DATA_HOME=/tmp/space/tests/xdg-data SPACE_DISABLE_AUDIO=1 SPACE_ASSETS_PATH=$(pwd)/assets make test
  • For targeted runs, include the command and a short result summary (e.g., “passed” / “failed: <test name>”).
  • Do not paste full test output into the commit message; keep it to a couple lines.

Practical: avoid shell-quoting footguns

  • Prefer writing the message to a file and committing with -F, especially if the body contains backticks:
    • cat > /tmp/commitmsg.txt <<'EOF' ... EOF
    • git commit -F /tmp/commitmsg.txt

Related Skills

Looking for an alternative to git-commit or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer