commit — community commit, kandev, community, ide skills

v1.0.0

이 스킬 정보

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.

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. 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

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
인공지능

widget-generator

Logo of f
f

prompts.chat 피드 시스템을 위한 사용자 지정 가능한 위젯 플러그인을 생성합니다

149.6k
0
인공지능

flags

Logo of vercel
vercel

리액트 프레임워크

138.4k
0
브라우저

pr-review

Logo of pytorch
pytorch

파이썬에서 텐서와 동적 신경망 구현 및 강력한 GPU 가속 지원

98.6k
0
개발자