commit — community commit, job-agent, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

このスキルについて

開発エージェントがストリームライン化されたgitコミットプロセスとベストプラクティスを必要とする場合に最適です。 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 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

開発エージェントがストリームライン化されたgitコミットプロセスとベストプラクティスを必要とする場合に最適です。 Create a git commit with a well-crafted message following project conventions

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

LLM、Vite、Nest.jsを使用して標準化されたgitコミットを作成するエージェントをEmpowerし、コミットメッセージを簡潔にし、`git status`、`git diff`、`git log`分析を通じてリポジトリの履歴を整理します。

おすすめ

開発エージェントがストリームライン化されたgitコミットプロセスとベストプラクティスを必要とする場合に最適です。

↓ 実現可能なユースケース 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 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?

開発エージェントがストリームライン化されたgitコミットプロセスとベストプラクティスを必要とする場合に最適です。 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. 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

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
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
開発者