commit — for Claude Code commit, job-agent, community, for Claude Code, ide skills, git status, git diff, git log --oneline -10, Create, following

v1.0.0
GitHub

About this Skill

Perfect for Development Agents needing streamlined git commit processes with best practices. Create a git commit with a well-crafted message following project conventions

Features

Create a git commit following best practices for this repository.
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

# Core Topics

for Claude Code git status git diff git log --oneline -10 Create following
thuyavan00 thuyavan00
[0]
[0]
Updated: 2/21/2026

Skill Overview

Start with fit, limitations, and setup before diving into the repository.

Perfect for Development Agents needing streamlined git commit processes with best practices. Create a git commit with a well-crafted message following project conventions

Core Value

Empowers agents to create standardized git commits using LLM, Vite, and Nest.js, ensuring concise commit messages and organized repository histories through `git status`, `git diff`, and `git log` analyses.

Ideal Agent Persona

Perfect for Development Agents needing streamlined git commit processes with best practices.

↓ Capabilities Granted for commit

Automating commit message drafting for new features and bug fixes
Generating standardized commit messages for enhancements and refactors
Analyzing recent commit history with `git log --oneline -10` for style consistency

! Prerequisites & Limits

  • Requires git repository access
  • Limited to repositories utilizing LLM, Vite, and Nest.js

About The Source

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

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?

Perfect for Development Agents needing streamlined git commit processes with best practices. 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. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for commit?

Key use cases include: Automating commit message drafting for new features and bug fixes, Generating standardized commit messages for enhancements and refactors, Analyzing recent commit history with `git log --oneline -10` for style consistency.

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?

Requires git repository access. Limited to repositories utilizing LLM, Vite, and 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. 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.

! Source Notes

This page is still useful for installation and source reference. Before using it, compare the fit, limitations, and upstream repository notes above.

Upstream Repository Material

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Upstream Source

commit

Install commit, an AI agent skill for AI agent workflows and automation. Explore features, use cases, limitations, and setup guidance.

SKILL.md
Readonly
Upstream Repository Material
The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.
Upstream Source

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

Related Skills

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

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

openclaw-release-maintainer is an AI agent skill for openclaw release maintainer.

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is an AI agent skill for use this skill when adding or changing framework feature flags in next.js internals.

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

pr-review is an AI agent skill for pytorch pr review skill.

★ 98.6k
⑂ 0
Developer