agentleFS
Sign inStart free
etejedawetejedaw/workflow-skills/skills/git-commit/SKILL.md

git-commit

Skill0 starsChanged 20 days agoApache-2.0View on GitHub

Create granular git commits following Conventional Commits with single-line messages in English and no AI signature, grouping changes by file. Use when the user asks to commit, "haz commit", "commitea" or runs /git-commit.

174 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use git-pr, github-pr-create and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • klauswgSkill

    git-pr

    Prepare, review, publish, or update a complete GitHub pull request for the current repository, including local commit readiness, safe push strategy, semantic title validation, repository-native PR templates, issue linking, and checks verification. Use when the user asks to draft, create, submit, publish, open, or update a pull request. Always require the user to review and explicitly approve the exact final PR before any push or GitHub write.

    Also in 11 projects that use this

  • mjun0812Skill

    github-pr-create

    Pull Requestを作成するSkill。現在のbranchからpull requestを作成する。言語指定可能。 ユーザーが「PR作って」「pull request作成して」のように依頼したら使うこと。

    Also in 3 projects that use this

  • MicrosoftSkill

    git-branch

    Branch management for implementation. Use when you need to create a branch, switch branches, checkout, or verify branching strategy before implementing code. Do not use for commits (use git-commit), pull requests (use pull-request), or advanced git operations (rebase, merge).

    Also in 4 projects that use this

  • klauswgSkill

    git-issue

    Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification. Use when the user asks to draft, file, submit, publish, edit, or refine a GitHub issue, bug report, feature request, performance issue, or technical proposal. Always require the user to review and explicitly approve the exact final issue before any GitHub write.

    Also in 3 projects that use this

  • gologo13Skill

    git-push

    Push current branch to origin and sync with remote updates; keywords: git, rebase. Use only on explicit request; before execution, review diffs and list impact scope.

    Also in 6 projects that use this

  • GoogleSkill

    github-pr-review

    Review a GitHub pull request and leave inline comments in a natural human reviewing voice, indistinguishable from comments typed by hand on the GitHub web UI. Deliberately bounded to defects a reader can settle by looking at the anchored line, rather than a deep audit, so every comment is cheap for the author to check. Scales to 2-20 comments by PR size, parallelises analysis across sub-agents, drafts for approval, then posts individually with human pacing. Use when the user says "review this PR", "review PR 123", pastes a github.com/.../pull/N link, or asks for comments on a pull request. Don't use for reviewing local uncommitted changes or a diff against a branch (use the `review` skill for that).

    Also in 4 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Git Commit

Configuración del proyecto

Las reglas de abajo son los valores por defecto. Si el CLAUDE.md del proyecto define otra cosa (scopes, idioma), manda lo del proyecto.

Reglas

  1. Conventional Commits: formato <type>(<scope>): <subject>. Tipos válidos: feat, fix, docs, style, refactor, test, chore, perf, build, ci.
  2. Una sola línea: el commit es solo el subject. Sin body, sin footer, sin trailers (ni -m "..." -m "..." ni HEREDOCs con body).
  3. Granular pero pragmático: cada commit cubre un único cambio lógico. Si el working tree mezcla cambios no relacionados, se dividen en commits separados, agrupando por archivo, no por hunk. Si un archivo mezcla 2-3 intenciones cercanas, va en un solo commit con un subject que abarque la intención dominante. Nada de commits "misc fixes" o "various updates".
  4. Sin firma: nunca agregar Co-Authored-By: Claude... ni ningún tipo de atribución de IA.
  5. En inglés.

Flujo

  1. git status y git diff para ver el estado.
  2. Si hay cambios no relacionados, agruparlos mentalmente por intención.
  3. Por cada grupo:
    • Stagear solo los archivos del grupo con git add <files>.
    • Elegir type y scope apropiados al cambio.
    • Subject en imperativo, en minúsculas, sin punto final.
    • git commit -m "<type>(<scope>): <subject>".
    • Si el commit falla por un hook, detenerse y mostrarle el error al usuario. No corregir ni reintentar.
  4. Verificar con git log --oneline -n <N>.

Scope

El módulo o la feature que toca el cambio (auth, users, invoices). En un monorepo, si no hay un módulo claro, el nombre de la app (api, web, landing) o repo para cambios transversales (workspaces, tooling, Docker). Antes de inventar un scope, revisa git log --oneline -n 30 y reutiliza los que ya existen.

Ejemplos

  • feat(auth): add register endpoint
  • fix(users): correct slug generation with accented names
  • refactor(events): extract date validation helper
  • docs(readme): document migration workflow
  • chore(deps): bump zod to 4.4.0

Prohibido

  • git add . o git add -A cuando hay múltiples grupos de cambios.
  • git add -p ni cirugía de hunks: el costo en tokens y complejidad supera el beneficio de granularidad fina. La unidad mínima de commit es el archivo.
  • --no-verify o cualquier otra forma de saltarse los hooks.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free