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 Work

by bartstc in bartstc/vite-ts-react-template

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits).

MITAuto-check passedDevelopment

Install Commit Work

skills CLI
$ npx skills add bartstc/vite-ts-react-template --skill commit-work -a claude-code

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

GitHub CLI
$ gh skill install bartstc/vite-ts-react-template commit-work --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/bartstc/vite-ts-react-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/commit-work .claude/skills/commit-work && 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-work
GitHub stars
122
Used in
3 other repos
Token cost
~623 tokens
SKILL.md length
312 words
Files
2 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits).

  • Works in 8 steps: Inspect the working tree before staging → Decide commit boundaries (split if needed) → Stage only what belongs in the next commit → …
  • The user asks to commit
  • SKILL.md covers Goal, Inputs to ask for (if missing), Workflow (checklist) and Deliverable
  • Calls git

What it does

Commit Work is an agent skill from bartstc/vite-ts-react-template. Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

Its SKILL.md is about 620 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/commit-message-template.md`).

It sits in Development, covering Commit messages. It works with React and Git. The repository describes itself as: This project provides a basic dev setup intended for Single Page Application (SPA) development. It contains key tools, settings for seamless DX, and an demo app presenting good… The licence is MIT.

When your agent uses it

  • The user asks to commit
  • Craft a commit message
  • Split work into multiple commits

Example prompts

  • “/commit-work”

Workflow steps

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

  1. Inspect the working tree before staging
  2. Decide commit boundaries (split if needed)
  3. Stage only what belongs in the next commit
  4. Review what will actually be committed
  5. Describe the staged change in 1-2 sentences (before writing the message)
  6. Write the commit message
  7. Run the smallest relevant verification
  8. Repeat for the next commit until the working tree is clean

What it can do on your machine

Read from SKILL.md and the folder at commit 6aa5c9c. 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 Work loads about 623 tokens when it runs, and up to ~710 if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 312 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~623
With references · SKILL.md plus every file in references/, read only if the agent opens them
~710

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 bartstc/vite-ts-react-template at commit 6aa5c9c, republished under its MIT licence (© bartstc). 312 words, ~623 tokens.

Download SKILL.mdSave it as .claude/skills/commit-work/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
commit-work
description
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

Commit work

Goal

Make commits that are easy to review and safe to ship:

  • only intended changes are included
  • commits are logically scoped (split when needed)
  • commit messages describe what changed and why

Inputs to ask for (if missing)

  • Single commit or multiple commits? (If unsure: default to multiple small commits when there are unrelated changes.)
  • Commit style: Conventional Commits are required.
  • Any rules: max subject length, required scopes.

Workflow (checklist)

  1. Inspect the working tree before staging
    • git status
    • git diff (unstaged)
    • If many changes: git diff --stat
  2. Decide commit boundaries (split if needed)
    • Split by: feature vs refactor, backend vs frontend, formatting vs logic, tests vs prod code, dependency bumps vs behavior changes.
    • If changes are mixed in one file, plan to use patch staging.
  3. Stage only what belongs in the next commit
    • Prefer patch staging for mixed changes: git add -p
    • To unstage a hunk/file: git restore --staged -p or git restore --staged <path>
  4. Review what will actually be committed
    • git diff --cached
    • Sanity checks:
      • no secrets or tokens
      • no accidental debug logging
      • no unrelated formatting churn
  5. Describe the staged change in 1-2 sentences (before writing the message)
    • "What changed?" + "Why?"
    • If you cannot describe it cleanly, the commit is probably too big or mixed; go back to step 2.
  6. Write the commit message
    • Use Conventional Commits (required):
      • type(scope): short summary
      • blank line
      • body (what/why, not implementation diary)
      • footer (BREAKING CHANGE) if needed
    • Prefer an editor for multi-line messages: git commit -v
    • Use references/commit-message-template.md if helpful.
  7. Run the smallest relevant verification
    • Run the repo's fastest meaningful check (unit tests, lint, or build) before moving on.
  8. Repeat for the next commit until the working tree is clean

Deliverable

Provide:

  • the final commit message(s)
  • a short summary per commit (what/why)
  • the commands used to stage/review (at minimum: git diff --cached, plus any tests run)

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

Files

SKILL.md and 1 other file (references) in .agents/skills/commit-work of bartstc/vite-ts-react-template.

  • SKILL.md
  • references/commit-message-template.md

Open the folder on GitHubat commit 6aa5c9c

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in bartstc/vite-ts-react-template, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Commit Work 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 Work compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit Work this skillbartstc/vite-ts-react-template1223 repos~623Automated safety check: PassMIT
Git Workflowsoftmaple/softmaple159—~814Automated safety check: PassApache-2.0
Commitalamenai/terrae245—~568Automated safety check: NotesMIT
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

Similar skills

  • Git Workflow

    softmaple/softmaple

    Softmaple Git branching, commits, pre-commit hooks, and pull requests.

    159 GitHub stars~814 tokensUpdated today
    DevelopmentAuto-check passed

  • Commit

    alamenai/terrae

    Create standardized git commits following Terrae's conventions

    245 GitHub stars~568 tokensUpdated 6 mo ago
    DevelopmentAuto-check: notes

  • 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 today
    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 today
    DevelopmentAuto-check passed

More from bartstc/vite-ts-react-template

  • GitHub Actions Templates

    bartstc/vite-ts-react-template

    Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications.

    122 GitHub starsUsed in 13 repos~1.9k tokens
    Auto-check passed

  • Playwright Page Objects

    bartstc/vite-ts-react-template

    A skill your agent uses when creating page objects or refactoring Playwright E2E tests for better maintainability with Page Object Model patterns.

    122 GitHub stars~1k tokensUpdated yesterday
    Auto-check: notes

  • Writing Spec

    bartstc/vite-ts-react-template

    Collaboratively write a feature spec with the developer. An agent skill from bartstc/vite-ts-react-template.

    122 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Explaining Code

    bartstc/vite-ts-react-template

    Explains code with visual diagrams and analogies. An agent skill from bartstc/vite-ts-react-template.

    122 GitHub starsUsed in 2 repos~154 tokens
    Auto-check passed

  • Building Blocks

    bartstc/vite-ts-react-template

    Frontend building block catalog — typed patterns for components, hooks, queries, mutations, stores, and models.

    122 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Test Building Blocks

    bartstc/vite-ts-react-template

    Test building block catalog — typed patterns for Storybook play-function tests, Vitest hook tests, Vitest unit tests, MSW handlers, and test data fixtures.

    122 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Commit Work

What does Commit Work do?

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Commit Work is an agent skill from bartstc/vite-ts-react-template. Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits).

When should I use Commit Work?

Commit Work fits situations like: the user asks to commit; craft a commit message; split work into multiple commits.

How do I install Commit Work in Claude Code?

Run `npx skills add bartstc/vite-ts-react-template --skill commit-work -a claude-code`. Or copy the skill folder (.agents/skills/commit-work in bartstc/vite-ts-react-template) into .claude/skills/commit-work in your project. Claude Code loads it when a task matches its description.

How do I install Commit Work in Codex?

Run `npx skills add bartstc/vite-ts-react-template --skill commit-work -a codex`. Or copy the skill folder (.agents/skills/commit-work in bartstc/vite-ts-react-template) into .agents/skills/commit-work in your project. Codex loads it when a task matches its description.

Can I use Commit Work 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 bartstc/vite-ts-react-template --skill commit-work -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-work, .gemini/skills/commit-work, .github/skills/commit-work and .opencode/skills/commit-work in your project.

What does Commit Work need to run?

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

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

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

About 623 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 87 tokens, read only when the agent opens those files.

What are the alternatives to Commit Work?

Skills that share tags, products or a category with Commit Work: Git Workflow (softmaple/softmaple, 159 stars), Commit (alamenai/terrae, 245 stars), React Router Release Notes Prep (remix-run/react-router, 57k stars) and ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit Work?

bartstc (a GitHub user) maintains it in bartstc/vite-ts-react-template, which has 122 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 6, 2026.

Source: bartstc/vite-ts-react-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.