Agent skill

Commit

by pheuter in pheuter/svelte-check-rs

Review current changes, commit, push, and optionally open a PR

MITAuto-check: notesDevelopment

Install Commit

skills CLI
$ npx skills add pheuter/svelte-check-rs --skill commit -a claude-code

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

GitHub CLI
$ gh skill install pheuter/svelte-check-rs 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/pheuter/svelte-check-rs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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
135
Token cost
~370 tokens
SKILL.md length
187 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Review current changes, commit, push, and optionally open a PR

  • Works in 4 steps: Read full diff if truncated. If changes… → Review changes for bugs, security issues… → Prepare commit → …
  • Tasks that involve Pull requests
  • SKILL.md covers User Request, Current Git State and Workflow
  • Calls git and gh

What it does

Commit is an agent skill from pheuter/svelte-check-rs. Review current changes, commit, push, and optionally open a PR

Its SKILL.md is about 370 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 Pull requests. It works with Git. The repository describes itself as: Sunsetted / archived. Rust Svelte 5 checker (Jan–Sep 2026) that helped inspire upstream native checking. Use official svelte-check; see README. The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/commit”

Workflow steps

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

  1. Read full diff if truncated. If changes above show "Output too large" with a file path, read that file first. Never review based on…
  2. Review changes for bugs, security issues (secrets, .env files), and incomplete work. If issues found, ask the user how to proceed.
  3. Prepare commit
  4. If PR requested: use gh pr create (add --draft if requested) with a clear title and description targeting the default branch. Follow PR…

What it can do on your machine

Read from SKILL.md and the folder at commit 134a25f. 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
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, 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 370 tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 187 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:43
    es** for bugs, security issues (secrets, .env files), and incomplete work. If issues found, ask the user how to proceed.

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 pheuter/svelte-check-rs at commit 134a25f, republished under its MIT licence (© pheuter). 187 words, ~370 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).
name
commit
description
Review current changes, commit, push, and optionally open a PR
argument-hint
[pr or draft pr]

Review the current git changes, create a commit, push to remote, and optionally open a pull request.

User Request

$ARGUMENTS

Current Git State

Status

!git status --short

Staged Changes

!git diff --cached

Unstaged Changes

!git diff

Recent Commits

!git log --oneline -5

Current Branch

!git branch --show-current

Default Branch

!git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'

Workflow

  1. Read full diff if truncated. If changes above show "Output too large" with a file path, read that file first. Never review based on partial output.

  2. Review changes for bugs, security issues (secrets, .env files), and incomplete work. If issues found, ask the user how to proceed.

  3. Prepare commit:

    • If PR requested and on the default branch, create a descriptive branch first
    • Run any format/lint commands specified in project guidelines — fix any issues
    • Stage relevant changes (skip secrets/generated files)
    • Commit following project conventions
    • Push (use -u origin <branch> for new branches)
  4. If PR requested: use gh pr create (add --draft if requested) with a clear title and description targeting the default branch. Follow PR conventions from CLAUDE.md.

If there are no changes to commit, let me know.

© pheuter, 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 .claude/skills/commit of pheuter/svelte-check-rs.

Open the folder on GitHubat commit 134a25f

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 skillpheuter/svelte-check-rs135—~370Automated safety check: NotesMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Open Code Review CLIalibaba/open-code-review44k—~3.1kAutomated safety check: PassApache-2.0
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    44k GitHub stars~3.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

More from pheuter/svelte-check-rs

  • Review PR Comments

    pheuter/svelte-check-rs

    Review PR comments, analyze validity, and create action items

    135 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Commit

What does Commit do?

Review current changes, commit, push, and optionally open a PR. Commit is an agent skill from pheuter/svelte-check-rs.

When should I use Commit?

Commit fits situations like: tasks that involve Pull requests.

How do I install Commit in Claude Code?

Run `npx skills add pheuter/svelte-check-rs --skill commit -a claude-code`. Or copy the skill folder (.claude/skills/commit in pheuter/svelte-check-rs) 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 pheuter/svelte-check-rs --skill commit -a codex`. Or copy the skill folder (.claude/skills/commit in pheuter/svelte-check-rs) 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 pheuter/svelte-check-rs --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 and gh).

Does Commit access the network?

SKILL.md contains no URLs. Its commands use git and gh, 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 notes only (mentions a .env file), nothing it rates as a warning. 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 370 tokens (SKILL.md is roughly 1.5k 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: Finishing a Development Branch (obra/superpowers, 296k stars), Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Open Code Review CLI (alibaba/open-code-review, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit?

pheuter (a GitHub user) maintains it in pheuter/svelte-check-rs, which has 135 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 5, 2026.

Source: pheuter/svelte-check-rs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.