Agent skill

Eisland Dev Git Commit

by JNTMTMTM in JNTMTMTM/eIsland

Analyze the current git status, review all staged and unstaged changes, and create a commit with a proper English commit message following conventional commit format.

GPL-3.0Auto-check passedDevelopment

Install Eisland Dev Git Commit

skills CLI
$ npx skills add JNTMTMTM/eIsland --skill eisland-dev-git-commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JNTMTMTM/eIsland eisland-dev-git-commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JNTMTMTM/eIsland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/eisland-dev-git-commit .claude/skills/eisland-dev-git-commit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
eisland-dev-git-commit
GitHub stars
320
Token cost
~1.1k tokens
SKILL.md length
436 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
GPL-3.0

At a glance

Analyze the current git status, review all staged and unstaged changes, and create a commit with a proper English commit message following conventional commit format.

  • Works in 7 steps: Check git status → Analyze the changes → Determine the scope → …
  • The user asks to commit
  • SKILL.md covers When to use, Process, Output and Edge cases, plus 1 more section
  • Calls git

What it does

Eisland Dev Git Commit is an agent skill from JNTMTMTM/eIsland. Analyze the current git status, review all staged and unstaged changes, and create a commit with a proper English commit message following conventional commit format. Use this skill whenever the user asks to "commit", "提交", "git commit", "analyze and commit", "check git status and commit", or wants to save their current changes to git.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Commit messages. It works with Git. The repository describes itself as: eIsland - A sleek, Apple Dynamic Island inspired floating widget for Windows, built with Electron. The licence is GPL-3.0.

When your agent uses it

  • The user asks to commit
  • Analyze and commit
  • Check git status and commit
  • Wants to save their current changes to git

Example prompts

  • “commit”
  • “git commit”
  • “analyze and commit”
  • “/eisland-dev-git-commit”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Check git status
  2. Analyze the changes
  3. Determine the scope
  4. Stage changes
  5. Create the commit message
  6. Commit
  7. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 411adb9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Eisland Dev Git Commit loads about 1.1k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 436 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JNTMTMTM/eIsland at commit 411adb9, republished under its GPL-3.0 licence (© JNTMTMTM). 436 words, ~1,076 tokens.

Download SKILL.mdSave it as .claude/skills/eisland-dev-git-commit/SKILL.md (or your agent's skills folder).
name
eisland-dev-git-commit
description
Analyze the current git status, review all staged and unstaged changes, and create a commit with a proper English commit message following conventional commit format. Use this skill whenever the user asks to "commit", "提交", "git commit", "analyze and commit", "check git status and commit", or wants to save their current changes to git.
author
JNTMTMTM

Git Status Analysis and Commit

Analyze the current git working tree, understand what changed and why, then create a well-formatted commit with an English message.

When to use

  • The user asks to commit their current changes
  • The user wants to analyze what's changed and create a commit
  • The user says "提交", "commit", "git commit", or similar
  • The user wants to review and save their work to git

Process

Step 1: Check git status

Run these commands to understand the current state:

bash
git status
git diff --stat
git diff --cached --stat

This tells you:

  • Which files are modified, added, or deleted
  • Which files are staged vs unstaged
  • The scope of changes
Step 2: Analyze the changes

For each changed file, read the diff to understand what was actually changed:

bash
git diff <file>        # for unstaged changes
git diff --cached <file>  # for staged changes

Categorize changes by type:

TypePrefixWhen to use
featfeatNew feature or user-facing functionality
fixfixBug fix
refactorrefactorCode restructuring without behavior change
stylestyleFormatting, whitespace, semicolons (no logic change)
docsdocsDocumentation only
testtestAdding or updating tests
chorechoreBuild config, dependencies, tooling
i18ni18nInternationalization changes
perfperfPerformance improvement
Step 3: Determine the scope

Look at which directories/modules were affected:

  • src/renderer/components/ → component name as scope
  • src/main/ → main process scope
  • i18n/ → i18n scope
  • docs/ → docs scope

If changes span multiple unrelated areas, consider making separate commits.

Step 4: Stage changes

If files are not yet staged, stage them:

bash
git add <files>

Or if the user wants to commit everything:

bash
git add -A
Step 5: Create the commit message

Use conventional commit format:

<type>(<scope>): <subject>

<body (optional)>

Rules:

  • Subject line: imperative mood, lowercase, no period at end, max 72 chars
  • Body (if needed): explain why not what (the diff shows what)
  • Use English for all commit messages
  • Reference issue numbers if applicable (e.g., Closes #123)

Examples:

feat(clipboard): add keyboard shortcuts for history navigation

fix(island): resolve drag position offset on high-DPI screens

refactor(stt): extract hooks from SttContent into separate files

docs(readme): update installation instructions for Windows

i18n(en-US): add missing translation keys for settings page
Show full SKILL.md (153 more words)Show less
Step 6: Commit

Create the commit:

bash
git commit -m "<commit message>"

For multi-line messages:

bash
git commit -m "<subject>" -m "<body>"
Step 7: Verify

Confirm the commit was created:

bash
git log -1 --oneline

Output

Return to the user:

  • The commit hash (short form)
  • The commit message
  • A brief summary of what was committed (file count, change types)

Edge cases

  • No changes: If git status shows nothing to commit, tell the user
  • Merge conflicts: If conflicts exist, inform the user and don't commit
  • User specifies message: If the user provides a specific commit message, use it (but still suggest improvements if it doesn't follow conventions)
  • Multiple logical changes: Suggest splitting into separate commits if changes are unrelated
  • Untracked files: Ask the user if they want to include new files

Important rules

  • Always use English for commit messages, regardless of the user's language
  • Follow conventional commits format strictly
  • Never commit without reviewing the actual diff content
  • Match the project's existing style — check recent commits with git log --oneline -10 for reference

© JNTMTMTM, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/eisland-dev-git-commit of JNTMTMTM/eIsland.

Open the folder on GitHubat commit 411adb9

Compare with similar skills

Eisland Dev Git Commit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Eisland Dev Git Commit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Eisland Dev Git Commit this skillJNTMTMTM/eIsland320—~1.1kAutomated safety check: PassGPL-3.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated today
    DevelopmentAuto-check passed

More from JNTMTMTM/eIsland

All 11 skills in this repo
  • Generate a release announcement markdown for eIsland. An agent skill from JNTMTMTM/eIsland.

    320 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Refactor a monolithic React component file into a standardized module structure with components/, hooks/, utils/, and config/ subdirectories.

    320 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Refactor a monolithic React component file into a standardized module structure with components/, hooks/, utils/, types/, and config/ subdirectories.

    320 GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • Add a new empty subpage (tab) to an existing eIsland settings section with page navigation support.

    320 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Eisland Dev Add SVG Icon

    JNTMTMTM/eIsland

    Add a new SVG icon to the project's icon enum system with matching test assertions.

    320 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Eisland Dev Update Docs

    JNTMTMTM/eIsland

    Update or create documentation in the eIsland VuePress docs site (web/eisland-web-docs).

    320 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Eisland Dev Git Commit

What does Eisland Dev Git Commit do?

Analyze the current git status, review all staged and unstaged changes, and create a commit with a proper English commit message following conventional commit format. Eisland Dev Git Commit is an agent skill from JNTMTMTM/eIsland. Analyze the current git status, review all staged and unstaged changes, and create a commit with a proper English commit message following conventional commit format.

When should I use Eisland Dev Git Commit?

Eisland Dev Git Commit fits situations like: the user asks to commit; analyze and commit; check git status and commit; wants to save their current changes to git.

How do I install Eisland Dev Git Commit in Claude Code?

Run `npx skills add JNTMTMTM/eIsland --skill eisland-dev-git-commit -a claude-code`. Or copy the skill folder (.agents/skills/eisland-dev-git-commit in JNTMTMTM/eIsland) into .claude/skills/eisland-dev-git-commit in your project. Claude Code loads it when a task matches its description.

How do I install Eisland Dev Git Commit in Codex?

Run `npx skills add JNTMTMTM/eIsland --skill eisland-dev-git-commit -a codex`. Or copy the skill folder (.agents/skills/eisland-dev-git-commit in JNTMTMTM/eIsland) into .agents/skills/eisland-dev-git-commit in your project. Codex loads it when a task matches its description.

Can I use Eisland Dev Git Commit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JNTMTMTM/eIsland --skill eisland-dev-git-commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eisland-dev-git-commit, .gemini/skills/eisland-dev-git-commit, .github/skills/eisland-dev-git-commit and .opencode/skills/eisland-dev-git-commit in your project.

What does Eisland Dev Git Commit need to run?

Going by SKILL.md and its folder, Eisland Dev Git Commit needs the command-line tools its instructions call (git).

Does Eisland Dev Git Commit access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Eisland Dev Git Commit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Eisland Dev Git Commit use?

Eisland Dev Git Commit is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Eisland Dev Git Commit use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Eisland Dev Git Commit?

Skills that share tags, products or a category with Eisland Dev Git Commit: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Eisland Dev Git Commit?

JNTMTMTM (a GitHub user) maintains it in JNTMTMTM/eIsland, which has 320 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.

Source: JNTMTMTM/eIsland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.