git-commit — for Claude Code git-commit, kubectl-mtv, community, for Claude Code, ide skills, forklift, kubectl-plugin, kubevirt, migration-tool, refactor

v1.0.0
GitHub

Acerca de este Skill

Escenario recomendado: Ideal for AI agents that need git commit convention. Resumen localizado: A kubectl plugin that helps users of Forklift migrate virtualization workloads from oVirt, VMware, OpenStack, and OVA files to KubeVirt on Kubernetes. It covers forklift, kubectl-plugin, kubevirt workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Características

Git Commit Convention
All commits must follow the Conventional Commits format with a DCO sign-off.
<type (<scope ): <short description
<body - explain WHY, not WHAT
Signed-off-by: Name <email

# Core Topics

for Claude Code forklift kubectl-plugin kubevirt migration-tool refactor
yaacov yaacov
[12]
[1]
Updated: 4/23/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for teams, 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 Quality floor passed for review
Review Score
10/11
Quality Score
64
Canonical Locale
en
Detected Body Locale
en

Escenario recomendado: Ideal for AI agents that need git commit convention. Resumen localizado: A kubectl plugin that helps users of Forklift migrate virtualization workloads from oVirt, VMware, OpenStack, and OVA files to KubeVirt on Kubernetes. It covers forklift, kubectl-plugin, kubevirt workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

¿Por qué usar esta habilidad?

Recomendacion: git-commit helps agents git commit convention. A kubectl plugin that helps users of Forklift migrate virtualization workloads from oVirt, VMware, OpenStack, and OVA files to KubeVirt on Kubernetes. This

Mejor para

Escenario recomendado: Ideal for AI agents that need git commit convention.

↓ Casos de uso accionables for git-commit

Caso de uso: Applying Git Commit Convention
Caso de uso: Applying All commits must follow the Conventional Commits format with a DCO sign-off
Caso de uso: Applying <type (<scope ): <short description

! Seguridad y limitaciones

  • Limitacion: All commits must follow the Conventional Commits format with a DCO sign-off.
  • Limitacion: docs Documentation only
  • Limitacion: Every commit must include Signed-off-by: Name <email (DCO sign-off). Use git commit -s to add it automatically.

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

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 workflows, 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?

Escenario recomendado: Ideal for AI agents that need git commit convention. Resumen localizado: A kubectl plugin that helps users of Forklift migrate virtualization workloads from oVirt, VMware, OpenStack, and OVA files to KubeVirt on Kubernetes. It covers forklift, kubectl-plugin, kubevirt workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install git-commit?

Run the command: npx killer-skills add yaacov/kubectl-mtv/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: Caso de uso: Applying Git Commit Convention, Caso de uso: Applying All commits must follow the Conventional Commits format with a DCO sign-off, Caso de uso: Applying <type (<scope ): <short description.

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?

Limitacion: All commits must follow the Conventional Commits format with a DCO sign-off.. Limitacion: docs Documentation only. Limitacion: Every commit must include Signed-off-by: Name <email (DCO sign-off). Use git commit -s to add it automatically..

↓ 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 yaacov/kubectl-mtv/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 Convention

All commits must follow the Conventional Commits format with a DCO sign-off.

Format

<type>(<scope>): <short description>

<body - explain WHY, not WHAT>

Signed-off-by: Name <email>

Commit Command

Always sign off with -s and include a body:

bash
1git commit -s -m "$(cat <<'EOF'
2fix(mcp): handle nil response from inventory API
3
4Prevents panic when provider inventory returns empty body.
5EOF
6)"

Type Prefixes

TypeWhen to use
featNew feature or capability
fixBug fix
refactorCode restructuring, no behavior change
docsDocumentation only
testAdding or updating tests
ciCI/CD changes (workflows, Makefile targets)
buildBuild system, dependencies, container images
choreMaintenance (deps update, cleanup)
perfPerformance improvement
styleFormatting, linting (no logic change)

Scope (Optional)

Area of the codebase in parentheses after the type:

ScopeArea
cliCLI commands (cmd/, pkg/cmd/)
mcpMCP server and tools (pkg/mcp/, cmd/mcpserver/)
inventoryInventory API and provider client
guideTechnical guide (guide/)
deployDeployment manifests (deploy/)
tuiTerminal UI (pkg/util/tui/)
e2eEnd-to-end tests (e2e/)

Omit scope for cross-cutting changes.

Title Rules

  • Imperative mood: "add", "fix", "update" (not "added", "fixes", "updates")
  • Lowercase after the colon
  • Max ~72 characters
  • No trailing period

Body

Required. Explain why the change was made, not what changed (the diff shows that). Separate from the title with a blank line. Even for small changes, provide a brief rationale.

Signed-off-by

Every commit must include Signed-off-by: Name <email> (DCO sign-off). Use git commit -s to add it automatically.

AI Co-authorship

When an AI agent contributes to a commit, ask the user whether to add a co-authorship trailer before committing. There are two levels:

  1. Full co-authorship -- the AI agent helped write production code (features, fixes, refactoring, etc.):
Co-authored-by: AI Agent <noreply@github.com>
  1. Unit-test co-authorship -- the AI agent only generated or helped write unit tests:
Co-authored-by: AI Agent (unit tests) <noreply@github.com>

Place the Co-authored-by line after the Signed-off-by line. If the user declines, omit it entirely.

Examples

feat(cli): add describe hook command

Allow users to inspect hook details including playbook
content and execution phase.

Signed-off-by: Yaacov Zamir <yzamir@redhat.com>

fix(mcp): handle nil response from inventory API

Prevents panic when provider inventory returns empty body.

Signed-off-by: Yaacov Zamir <yzamir@redhat.com>
Co-authored-by: AI Agent <noreply@github.com>

docs(guide): add chapter on warm migration workflow

Covers warm migration lifecycle, cutover timing, and
snapshot scheduling for vSphere providers.

Signed-off-by: Yaacov Zamir <yzamir@redhat.com>

refactor(tui): extract table rendering into reusable component

Reduces duplication across get commands and makes it
easier to add new table-based views.

Co-authored-by: AI Agent <noreply@github.com>

Signed-off-by: Yaacov Zamir <yzamir@redhat.com>

test(cli): add unit tests for describe hook command

Covers edge cases for missing hooks, empty playbooks,
and invalid hook phases.

Co-authored-by: AI Agent (unit tests) <noreply@github.com>

Signed-off-by: Yaacov Zamir <yzamir@redhat.com>

build: update forklift dependency to latest v1beta1

Picks up new DynamicProvider CRD types needed for
custom provider support.

Signed-off-by: Yaacov Zamir <yzamir@redhat.com>

Breaking Changes

Add ! after type/scope and include BREAKING CHANGE: in the body:

feat(mcp)!: rename mtv_query tool to mtv_read

BREAKING CHANGE: mtv_query has been renamed to mtv_read.
Update all MCP client configurations.

Signed-off-by: Yaacov Zamir <yzamir@redhat.com>

Habilidades relacionadas

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

Ver todo

openclaw-release-maintainer

Logo of openclaw
openclaw

Resumen localizado: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 333.8k
⑂ 0
Inteligencia Artificial

widget-generator

Logo of f
f

Resumen localizado: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

★ 149.6k
⑂ 0
Inteligencia Artificial

flags

Logo of vercel
vercel

Resumen localizado: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 138.4k
⑂ 0
Navegador

pr-review

Logo of pytorch
pytorch

Resumen localizado: Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 98.6k
⑂ 0
Desarrollador