agentleFS
brayandiazcbrayandiazc/project-starter-template-es-ai/.claude/skills/commit/SKILL.md

commit

Skill15 starsChanged 2 months agoMITView on GitHub

Escribe un mensaje de Conventional Commits para los cambios en stage y crea el commit, incluyendo la línea de coautoría de atribución de IA. Úsalo cuando la persona pida hacer commit, escribir un mensaje de commit o guardar cambios (p. ej. "haz commit de esto", "escribe un mensaje de commit para estos cambios"). No hace push.

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use act-on-feedback, generate-run-commands 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.
  • MicrosoftSkill

    act-on-feedback

    Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

    Also in 4 projects that use this

  • MicrosoftSkill

    generate-run-commands

    Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

    Also in 4 projects that use this

  • shawn-dumasSkill

    validate-plan

    Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.

    Also in 5 projects that use this

  • MindgamesSkill

    branch

    Use when a user asks to create a new local git branch and start issue work (for example, "create branch" or "start working on issue XYZ"). Use this for issue-based branch naming in the `type/scope-short-description` pattern and for always syncing local `main` from `origin/main` before creating the new branch, creating the local tracking `main` branch first when needed.

    Also in 9 projects that use this

  • decocmsSkill

    add-mcp-tools

    Guide for adding new MCP tools with consistent patterns for schemas, tool definitions, registry updates, and Better Auth integration

    Also in 3 projects that use this

  • mitsuhikoSkill

    oebb-scotty

    Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NO hagas push, NO modifiques (amend) ni reescribas el historial existente, y NO incluyas cambios no relacionados — mantén cada commit …

    line 24

“Common” is measured: kept by at least 6 in 10 of the 167 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Crea un commit bien formado para los cambios actuales.

  1. Lee CONTRIBUTING.md para conocer las reglas de commit del proyecto (tipos permitidos, convenciones de scope, estilo del asunto, footers requeridos). Sigue ese documento por encima de los valores por defecto de abajo.
  2. Inspecciona lo que está en stage con git status y git diff --staged. Si no hay nada en stage, revisa git diff y agrega al stage los archivos correspondientes; pregunta antes de hacer stage si es ambiguo.
  3. Formatea antes de commitear — el CI lo exige: si hay archivos .md en el cambio, corre bash .github/scripts/format.sh (Prettier) y re-agrega al stage lo que cambie; si el proyecto ya tiene su propio [COMANDO_LINT]/formatter, córrelo también sobre los archivos tocados.
  4. Redacta un mensaje de Conventional Commits:
    • Formato: <type>(<optional scope>): <short imperative subject>
    • Tipos comunes: feat, fix, docs, refactor, test, chore, build, ci.
    • Mantén el asunto por debajo de ~72 caracteres; añade un cuerpo que explique el porqué cuando el cambio no sea trivial.
    • Usa ! o un footer BREAKING CHANGE: para cambios que rompen compatibilidad.
  5. Para trabajo asistido por IA, añade la línea de atribución/coautoría en el footer según lo definido en CONTRIBUTING.md (un trailer Co-Authored-By:).
  6. Crea el commit. Muestra el mensaje final a la persona.

Ejemplo de asunto: feat(auth): add password reset via email.

NO hagas push, NO modifiques (amend) ni reescribas el historial existente, y NO incluyas cambios no relacionados — mantén cada commit enfocado.

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.