Perfecto para agentes de revisión de código que necesitan un control de versiones y gestión de commits de Git preciso. Stage changes, run pre-commit hooks, and create a well-formatted git commit

How do I install commit?

Run the command: npx killer-skills add captainsparrow10/LLM-ENGINEERS-HANDBOOK/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: Automatización de la escritura de mensajes de commit, Generación de resúmenes de cambios con `git diff --stat`, Depuración de problemas de commit con la configuración selectiva de archivos.

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?

Requiere la instalación y configuración de Git. Nunca compromete archivos como `.env` que contienen información sensible como `HUGGINGFACE_ACCESS_TOKEN`.

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 Workflow

Name: commit
Availability: InStock
Author: captainsparrow10

Create a clean, well-documented git commit following this project's conventions.

Step 1: Review changes

bash
1git status
2git diff --stat

Show the user a summary of what will be committed.

Step 2: Stage files

Stage files selectively (never git add . or git add -A blindly):

bash
1# Stage specific files
2git add <file1> <file2> ...

Files to NEVER commit

Pattern	Reason
`.env`	Contains `HUGGINGFACE_ACCESS_TOKEN`
`*.pyc`, `__pycache__/`	Compiled Python
`.DS_Store`	macOS junk
`model_output/`	Downloaded models
`data/eval_results/`	Generated evaluation data
`output/`	Pipeline outputs
`.claude/settings.local.json`	Personal Claude settings
`.claude/CLAUDE.local.md`	Personal Claude memory

If $ARGUMENTS says "all" or "todo", stage all modified/untracked files except those above.

Step 3: Pre-commit hooks

This project has pre-commit hooks configured in .pre-commit-config.yaml:

ruff (linter) - auto-fixes code style
ruff-format (formatter) - auto-formats code
gitleaks - scans for leaked secrets

If a hook fails:

The commit is aborted (it did NOT happen)
Fix the issues (ruff usually auto-fixes, just re-stage)
Create a NEW commit (never --amend after a hook failure - that would modify the wrong commit)

Step 4: Commit message format

Use Conventional Commits:

<type>(<scope>): <description>

[optional body]

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Types

Type	When to use
`feat`	New feature or functionality
`fix`	Bug fix
`docs`	Documentation changes (README, CLAUDE.md, comments)
`refactor`	Code restructuring without behavior change
`chore`	Maintenance (deps, configs, cleanup)
`style`	Formatting, linting (no logic change)
`test`	Adding or modifying tests
`perf`	Performance improvements
`ci`	CI/CD changes

Scopes (optional, use the most relevant)

Scope	Files
`inference`	model/inference/, infrastructure/inference_pipeline_api.py
`rag`	application/rag/
`eval`	model/evaluation/
`training`	model/finetuning/
`etl`	application/crawlers/, configs/digital_data_etl_*
`dataset`	application/dataset/
`settings`	settings.py, .env, configs/
`deps`	pyproject.toml, poetry.lock
`infra`	docker-compose.yml, ZenML configs

Examples

feat(rag): Add author filtering to Qdrant search
fix(inference): Add task parameter to HuggingFaceEndpoint
docs: Rewrite README for local-only setup
chore(deps): Upgrade langchain-huggingface to 1.2.0
refactor(eval): Replace OpenAI judge with HuggingFace

Step 5: Create the commit

Use HEREDOC for proper message formatting:

bash
1git commit -m "$(cat <<'EOF'
2<type>(<scope>): <description>
3
4<body if needed>
5
6Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
7EOF
8)"

Step 6: Verify

bash
1git log --oneline -3

Show the user the new commit hash and message.

After the commit

Do NOT push automatically. Tell the user they can push with /push or git push.

If pre-commit hook fails

Check what failed: usually ruff auto-fixed files
Re-stage the auto-fixed files: git add <fixed-files>
Create a NEW commit (do NOT use --amend)
If gitleaks fails: a secret was detected. Remove it from the staged files before retrying.

commit — community commit, LLM-ENGINEERS-HANDBOOK, community, ide skills

Acerca de este Skill

Killer-Skills Review

¿Por qué usar esta habilidad?

Mejor para

↓ Casos de uso accionables for commit

! Seguridad y limitaciones

Why this page is reference-only

Source Boundary

Decide The Next Action Before You Keep Reading Repository Material

Start With Installation And Validation

Cross-Check Against Trusted Picks

Move To Workflow Collections For Team Rollout

Browser Sandbox Environment

⚡️ Ready to unleash?

FAQ & Installation Steps

? Frequently Asked Questions

What is commit?