commit — community commit, job-agent, community, ide skills

v1.0.0
GitHub

이 스킬 정보

개발 에이전트가 개발 프로세스를 간소화하고 최고의 관행을 필요로 할 때 완벽합니다. Create a git commit with a well-crafted message following project conventions

thuyavan00 thuyavan00
[0]
[0]
Updated: 2/21/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/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
Review Score
7/11
Quality Score
48
Canonical Locale
en
Detected Body Locale
en

개발 에이전트가 개발 프로세스를 간소화하고 최고의 관행을 필요로 할 때 완벽합니다. Create a git commit with a well-crafted message following project conventions

이 스킬을 사용하는 이유

LLM, Vite 및 Nest.js를 사용하여 표준화된 git 커밋을 생성할 수 있는 에이전트를 강화하여 커밋 메시지를 간결하게 유지하고 `git status`, `git diff` 및 `git log` 분석을 통해 저장소 기록을 구성합니다.

최적의 용도

개발 에이전트가 개발 프로세스를 간소화하고 최고의 관행을 필요로 할 때 완벽합니다.

↓ 실행 가능한 사용 사례 for commit

새로운 기능 및 버그 수정을 위한 커밋 메시지 초안 자동화
강화 및 리팩토링을 위한 표준화된 커밋 메시지 생성
스타일 일관성을 보장하기 위해 `git log --oneline -10`를 사용하여 최근 커밋 기록 분석

! 보안 및 제한 사항

  • git 저장소 액세스가 필요
  • LLM, Vite 및 Nest.js를 사용하는 저장소에만 제한

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 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 commit?

개발 에이전트가 개발 프로세스를 간소화하고 최고의 관행을 필요로 할 때 완벽합니다. Create a git commit with a well-crafted message following project conventions

How do I install commit?

Run the command: npx killer-skills add thuyavan00/job-agent/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: 새로운 기능 및 버그 수정을 위한 커밋 메시지 초안 자동화, 강화 및 리팩토링을 위한 표준화된 커밋 메시지 생성, 스타일 일관성을 보장하기 위해 `git log --oneline -10`를 사용하여 최근 커밋 기록 분석.

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 저장소 액세스가 필요. LLM, Vite 및 Nest.js를 사용하는 저장소에만 제한.

↓ 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 thuyavan00/job-agent/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

Git Commit Skill

Create a git commit following best practices for this repository.

Process

  1. Analyze the current state - Run these in parallel:

    • git status - See all untracked and modified files
    • git diff - See both staged and unstaged changes
    • git log --oneline -10 - Review recent commit message style

  2. Draft commit message:

    • Summarize the nature of changes (new feature, enhancement, bug fix, refactor, docs, etc.)
    • Be concise (1-2 sentences) focusing on "why" rather than "what"
    • Use imperative mood (e.g., "add", "fix", "update", not "added", "fixed")
    • Follow the style of recent commits in this repo
    • Match scope to actual changes:
      • "add" = wholly new feature/file
      • "update" = enhancement to existing feature
      • "fix" = bug fix
      • "refactor" = code restructuring
      • "feat" = new feature (if using conventional commits)
      • "chore" = maintenance tasks

  3. Stage and commit - Run these sequentially:

    • Stage relevant files by name (prefer specific files over git add -A)
    • Create commit with message ending in: 
      Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
    • Run git status after commit to verify success

  4. Format commit messages using HEREDOC:

    bash
    1git commit -m "$(cat <<'EOF'
2Your commit message here.
3
4Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
5EOF
6)"

Safety Rules

  • NEVER update git config
  • NEVER run destructive commands without user confirmation:
    • git push --force
    • git reset --hard
    • git checkout .
    • git clean -f
    • git branch -D
  • NEVER skip hooks (--no-verify, --no-gpg-sign) unless explicitly requested
  • NEVER amend commits unless explicitly requested
  • CRITICAL: If pre-commit hook fails, fix the issue and create a NEW commit (don't use --amend)
  • Prefer staging specific files by name rather than git add -A or git add .
  • Don't commit if there are no changes
  • Don't commit sensitive files (.env, credentials, etc.)

Arguments

  • No arguments: Commit all current changes
  • With file paths: Commit only specified files

Example Usage

/commit
/commit src/components/Button.tsx

관련 스킬

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
개발자