commit — community commit, kandev, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

このスキルについて

Conventional Commits規約に従った標準化されたgitコミットメッセージを必要とする開発エージェントに適しています。 Stage and commit changes using Conventional Commits. Use when there are dirty/staged files to commit, the user says commit, or before pushing a PR.

kdlbs kdlbs
[9]
[1]
Updated: 3/8/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
Review Score
7/11
Quality Score
48
Canonical Locale
en
Detected Body Locale
en

Conventional Commits規約に従った標準化されたgitコミットメッセージを必要とする開発エージェントに適しています。 Stage and commit changes using Conventional Commits. Use when there are dirty/staged files to commit, the user says commit, or before pushing a PR.

このスキルを使用する理由

Conventional Commits形式を使用して構造化されたgitコミットを作成するエージェントを可能にし、git-cliffおよびCI検証を介して変更ログとリリースノートの自動生成を可能にし、cliff.tomlおよびpr-title.ymlを介して検証します。

おすすめ

Conventional Commits規約に従った標準化されたgitコミットメッセージを必要とする開発エージェントに適しています。

↓ 実現可能なユースケース for commit

新機能のコミットメッセージを'feat'タイプで自動化する
'fix'タイプのコミットからリリースノートを生成する
Conventional Commits規約に従ったコミットメッセージの検証

! セキュリティと制限

  • gitの設定が必要
  • Conventional Commits形式のみ対応
  • git-cliffおよびCI検証ツールに依存

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - 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 commit?

Conventional Commits規約に従った標準化されたgitコミットメッセージを必要とする開発エージェントに適しています。 Stage and commit changes using Conventional Commits. Use when there are dirty/staged files to commit, the user says commit, or before pushing a PR.

How do I install commit?

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

What are the use cases for commit?

Key use cases include: 新機能のコミットメッセージを'feat'タイプで自動化する, 'fix'タイプのコミットからリリースノートを生成する, Conventional Commits規約に従ったコミットメッセージの検証.

Which IDEs are compatible with 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 commit?

gitの設定が必要. Conventional Commits形式のみ対応. git-cliffおよびCI検証ツールに依存.

↓ 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 kdlbs/kandev/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 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

commit

Install commit, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

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

Commit

Create a git commit following this project's Conventional Commits convention. These messages are used by git-cliff (cliff.toml) to auto-generate changelogs and release notes. PRs are squash-merged, so the PR title becomes the commit on main — CI validates it via pr-title.yml.

Format

type: lowercase description

Allowed Types

TypeUse forIn changelog?
featNew featuresYes (Features)
fixBug fixesYes (Bug Fixes)
perfPerformance improvementsYes (Performance)
refactorCode refactoringYes (Refactoring)
docsDocumentation changesYes (Documentation)
choreMaintenance, deps, configsNo
ciCI/CD changesNo
testTest-only changesNo

Rules

  • Subject must start with a lowercase letter
  • Scope is optional: feat(ui): add dialog is valid
  • Include PR/issue number when relevant: feat: add release notes (#295)
  • Breaking changes: add ! after type: feat!: remove legacy API
  • Keep the first line under 72 characters

Examples

feat: add release notes dialog
fix: flaky test in orchestrator (#292)
refactor: extract session handler into separate module
chore: update dependencies
ci: add PR title linting workflow

Steps

  1. Run git status and git diff to understand all changes
  2. Review recent commits with git log --oneline -10 to match project style
  3. Stage relevant files (prefer specific files over git add -A)
  4. Write a commit message following the format above
  5. If changes span multiple concerns, consider separate commits
  6. After committing, run make fmt then make lint to verify

関連スキル

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

すべて表示

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

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

React フレームワーク

★ 138.4k
⑂ 0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク（強力なGPUアクセラレーション）

★ 98.6k
⑂ 0
開発者