New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Commit

by aviatesk in aviatesk/JET.jl

A skill your agent uses when writing a commit message, and MUST invoke before creating any git commit.

MITAuto-check passedDevelopment

Install Commit

skills CLI
$ npx skills add aviatesk/JET.jl --skill commit -a claude-code

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

GitHub CLI
$ gh skill install aviatesk/JET.jl 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/aviatesk/JET.jl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/commit .claude/skills/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
commit
GitHub stars
883
Token cost
~1k tokens
SKILL.md length
392 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when writing a commit message, and MUST invoke before creating any git commit.

  • Works in 3 steps: Explain the concrete problem,… → Explain the approach used to implement… → Mention important caveats, follow-up…
  • Writing a commit message
  • SKILL.md covers Title format, Body, Line length and GitHub references, plus 2 more sections
  • Calls git

What it does

Commit is an agent skill from aviatesk/JET.jl. Use when writing a commit message, and MUST invoke before creating any git commit. Provides commit message format and safety rules.

Its SKILL.md is about 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: A code analyzer for Julia. No need for additional type annotations. The licence is MIT.

When your agent uses it

  • Writing a commit message
  • MUST invoke before creating any git commit

Example prompts

  • “/commit”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Explain the concrete problem, limitation, or goal motivating the change.
  2. Explain the approach used to implement the change.
  3. Mention important caveats, follow-up work, performance notes, or test

What it can do on your machine

Read from SKILL.md and the folder at commit 19c3b4c. 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

Commit loads about 1k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 392 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~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 aviatesk/JET.jl at commit 19c3b4c, republished under its MIT licence (© aviatesk). 392 words, ~1,039 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).
name
commit
description
Use when writing a commit message, and MUST invoke before creating any git commit. Provides commit message format and safety rules.

Message guideline

Title format

Use "component: Brief summary" format and imperative mood for the commit title.

Examples:

  • "toplevel: Support versioned module expressions"
  • "optanalyzer: Analyze runtime dispatches on IRCode"
  • "test: Integrate JET failures with Test recording"

Body

Write a body by default, including for small, self-contained changes. Do not treat a descriptive title as a reason to omit the body. When little explanation is needed, briefly state the motivation and implementation.

Organize body paragraphs in this order and omit any paragraph that is not relevant:

  1. Explain the concrete problem, limitation, or goal motivating the change. For user-facing work, describe the resulting capability or behavior. For internal work, explain the engineering reason without inventing a user-visible impact. Include a small code example when it adds clarity.
  2. Explain the approach used to implement the change.
  3. Mention important caveats, follow-up work, performance notes, or test coverage when relevant.

Write body paragraphs as explanatory prose with explicit subjects:

  • Prefer a concrete subject such as the affected component or newly introduced type.
  • Use This change or This commit when describing the patch as a whole.
  • Use The implementation when explaining the mechanism.
  • Do not omit a subject merely to avoid we or I.

Use backticks for code elements such as function names, variables, and paths.

Show full SKILL.md (180 more words)Show less

Line length

Ensure the maximum line length never exceeds 72 characters. Never rely on Git or an editor to wrap the message automatically.

Before every commit, write the complete message to a uniquely named temporary file with explicit line breaks, then commit with GIT_EDITOR=true git -c core.hooksPath=.githooks commit -F <message-file>. Do not use repeated git commit -m arguments for a multi-paragraph message.

The command-local core.hooksPath setting automatically runs the tracked commit-msg hook and rejects lines longer than 72 characters. Never use --no-verify to bypass it.

GitHub references

When referencing external GitHub PRs or issues, use proper GitHub interlinking format: "owner/repo#123".

Co-author trailer

If you wrote code yourself, include a co-author trailer at the end of the commit message, for example:

Co-Authored-By: GPT-5.6 Sol <noreply@openai.com>

Adjust the model name as appropriate. When simply asked to write a commit message without having written the code, do not add the trailer.

Examples

The examples below are adapted from JET history. Co-author trailers are omitted.

Behavior change

Reference: 2d06d461fe1d9304972bdb4887af688d0edab4f0

optanalyzer: Analyze runtime dispatches on `IRCode`

`OptAnalyzer` converted `OptimizationState` to `CodeInfo` before
Compiler cache transformation. This interfered with the Julia 1.13
inlining-cost lifecycle and required restoring the cost manually.

`OptAnalyzer` now analyzes the final `IRCode` after
`Compiler.optimize` instead. A lightweight state adapter provides report
signatures and locations. The implementation recomputes frame
eligibility instead of maintaining FIFO state.

This change preserves Julia 1.12 compatibility while allowing Compiler
to own cache transformation and inlining-cost computation.
Bug fix

Reference: 9bc9057b1c257b8905e8c8b4d888c88cc89e9378

toplevel: Support versioned module expressions

`virtual_process` assumed that a module body was always the third
argument of a `module` expression. Julia 1.14 syntax adds a syntax
version argument, shifting the module body and preventing definitions
inside the module from being analyzed correctly.

The implementation now takes the module body from the final expression
argument. This change supports both legacy and versioned module layouts.

Safety guidelines

See the "Git operations" section in AGENTS.md.

© aviatesk, MIT. 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/commit of aviatesk/JET.jl.

Open the folder on GitHubat commit 19c3b4c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in aviatesk/JET.jl, which our catalogue first saw on October 7, 2026.

Compare with similar skills

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.

Commit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit this skillaviatesk/JET.jl883—~1kAutomated safety check: PassMIT
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-skills102k2 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

  • ToolJet Multi-Repo Commit

    ToolJet/ToolJet

    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.

    102k 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

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    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

  • Saleor Commit Workflow

    saleor/saleor

    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 yesterday
    DevelopmentAuto-check passed

More from aviatesk/JET.jl

  • Run Test

    aviatesk/JET.jl

    A skill your agent uses when choosing or running JET tests after code changes.

    883 GitHub stars~643 tokensUpdated yesterday
    Auto-check passed

  • Write Test

    aviatesk/JET.jl

    A skill your agent uses when adding or modifying JET tests. An agent skill from aviatesk/JET.jl.

    883 GitHub stars~777 tokensUpdated yesterday
    Auto-check passed

  • Changelog

    aviatesk/JET.jl

    Invoke before committing user-facing JET changes such as features, bug fixes, compatibility changes, or deprecations.

    883 GitHub stars~492 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Commit

What does Commit do?

A skill your agent uses when writing a commit message, and MUST invoke before creating any git commit. jl. Use when writing a commit message, and MUST invoke before creating any git commit.

When should I use Commit?

Commit fits situations like: writing a commit message; MUST invoke before creating any git commit.

How do I install Commit in Claude Code?

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

How do I install Commit in Codex?

Run `npx skills add aviatesk/JET.jl --skill commit -a codex`. Or copy the skill folder (.agents/skills/commit in aviatesk/JET.jl) into .agents/skills/commit in your project. Codex loads it when a task matches its description.

Can I use 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 aviatesk/JET.jl --skill 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/commit, .gemini/skills/commit, .github/skills/commit and .opencode/skills/commit in your project.

What does Commit need to run?

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

Does 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 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 Commit use?

Commit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit use?

About 1k tokens (SKILL.md is roughly 4.2k 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 Commit?

Skills that share tags, products or a category with 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, 102k 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 Commit?

aviatesk (a GitHub user) maintains it in aviatesk/JET.jl, which has 883 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.

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