git-commit-en

Generates Conventional Commits messages in English from session context and staged git diff.

IndexedMIT

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/tomyou666-git-commit-en

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Generates Conventional Commits messages in English from session context and staged git diff. Use only when the user explicitly invokes this skill (e.g. /git-commit-en).

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/git-commit-en

What's inside

Skill name: git-commit-en
Description: Generates Conventional Commits messages in English from session context and staged git diff. Use only when the user explicitly invokes this skill (e.g. /git-commit-en).
License: MIT
Instructions: 34 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Git Commit EN

## Instructions

Create a commit message in English by combining:

- What was discussed in the current session.
- The staged diff preview from this exact command:
  - `git diff --staged | cut -c 1-2000`

## Workflow

1. Read the session context and identify intent (why the change exists).
2. Run `git diff --staged | cut -c 1-2000` and extract key change points.
3. Pick an appropriate Conventional Commits type (`feat`, `fix`, `docs`, `refactor`, `test`, `chore`, etc.).
4. Write the message in this format:

```text
type(scope): short summary

line 1 explaining why/impact
line 2 optional
line 3 optional
```

## Output Rules

- Follow Conventional Commits.
- Title must be a single concise line.
- Body must be at most 3 lines total.
- Keep the body focused on purpose/impact, not noisy implementation detail.
- If scope is unclear, omit scope rather than guessing.

From tomyou666/skills, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Sep 27, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/tomyou666/skills
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from tomyou666

Cite this page

git-commit-en skill. Agent Mart. https://agentmart.dev/skills/tomyou666-git-commit-en (last updated 2026-10-24)