New: 98,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 Changes

by foldkit in foldkit/foldkit

Create a git commit in the Foldkit monorepo with changeset enforcement and formatting.

MITAuto-check passedDevelopment

Install Commit Changes

skills CLI
$ npx skills add foldkit/foldkit --skill commit-changes -a claude-code

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

GitHub CLI
$ gh skill install foldkit/foldkit commit-changes --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/foldkit/foldkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/commit-changes .claude/skills/commit-changes && 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-changes
GitHub stars
918
Token cost
~1.2k tokens
SKILL.md length
680 words
Files
2
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Create a git commit in the Foldkit monorepo with changeset enforcement and formatting.

  • Works in 5 steps: Inspect the worktree with git status… → Identify changed files owned by the… → Check whether changed files touch any… → …
  • The user asks Codex to commit current changes
  • SKILL.md covers Workflow, Commit Message Rules and Boundaries
  • Calls git, pnpm and changeset

What it does

Commit Changes is an agent skill from foldkit/foldkit. Create a git commit in the Foldkit monorepo with changeset enforcement and formatting. Use when the user asks Codex to commit current changes, make a commit, create a changeset-backed commit, or prepare a local Foldkit commit.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Commit messages and Monorepo tooling. It works with Git. The licence is MIT.

When your agent uses it

  • The user asks Codex to commit current changes
  • Create a changeset-backed commit
  • Prepare a local Foldkit commit

Example prompts

  • “/commit-changes”

Workflow steps

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

  1. Inspect the worktree with git status --short, git diff HEAD, git branch --show-current, and git log --oneline -10.
  2. Identify changed files owned by the current task. Do not stage unrelated user changes.
  3. Check whether changed files touch any published package path
  4. If a published package changed, inspect .changeset/*.md excluding README.md and config.json. Verify a changeset covers each changed package.
  5. If a changed published package has no covering changeset, create one

What it can do on your machine

Read from SKILL.md and the folder at commit d21db42. 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
    • pnpm
    • changeset

    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 pnpm, 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 Changes loads about 1.2k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 680 words of instructions outside code blocks.

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

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 foldkit/foldkit at commit d21db42, republished under its MIT licence (© foldkit). 680 words, ~1,247 tokens.

Download SKILL.mdSave it as .claude/skills/commit-changes/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
commit-changes
description
Create a git commit in the Foldkit monorepo with changeset enforcement and formatting. Use when the user asks Codex to commit current changes, make a commit, create a changeset-backed commit, or prepare a local Foldkit commit.

Commit Changes

Create a single local commit for Foldkit changes. Do not push.

Workflow

  1. Inspect the worktree with git status --short, git diff HEAD, git branch --show-current, and git log --oneline -10.
  2. Identify changed files owned by the current task. Do not stage unrelated user changes.
  3. Check whether changed files touch any published package path:
    • packages/foldkit/ -> foldkit
    • packages/ui/ -> @foldkit/ui
    • packages/devtools/ -> @foldkit/devtools
    • packages/create-foldkit-app/ -> create-foldkit-app
    • packages/vite-plugin-foldkit/ -> @foldkit/vite-plugin
    • packages/devtools-mcp/ -> @foldkit/devtools-mcp
    • packages/oxlint-plugin-foldkit/ -> @foldkit/oxlint-plugin
  4. If a published package changed, inspect .changeset/*.md excluding README.md and config.json. Verify a changeset covers each changed package.
  5. If a changed published package has no covering changeset, create one:
markdown
---
'package-name': patch
---

Concise description of the change.

Use an empty changeset, a file holding only the two frontmatter delimiters, for an internal change with no user-facing effect, such as a pure refactor, a move between modules that leaves the published surface and behavior unchanged, or a test-only change. It satisfies changeset status without adding a release entry. Use patch for bug fixes, docs, and metadata changes. Use minor for new features, non-breaking API additions, and breaking changes while the project is pre-1.0. Do not use major.

For breaking changes, include a brief migration note in the changeset description.

  1. Run pnpm format and require a successful exit. If the command times out or does not report an exit status, do not assume it succeeded. Inspect formatting changes and stage only files that belong to the requested commit. For a targeted run, ./node_modules/.bin/oxfmt <paths> writes the files; do not add a --write flag.
  2. Run pnpm format:check and require a successful exit. A targeted ./node_modules/.bin/oxfmt --check <paths> is also valid when only those files are in scope.
  3. Stage relevant files with git add.
  4. Create one Conventional Commit with git commit.
  5. Verify the final commit message with git log -1 --format=%B. If any body line is longer than 80 characters, amend the commit before stopping. Re-check the subject, scope, author, and branch shape after every amend.
Show full SKILL.md (357 more words)Show less

Commit Message Rules

  • Use a valid scope from AGENTS.md when one scope describes the commit's primary intent. If no valid scope cleanly describes the whole change set, omit the scope.
  • Inspect the full staged diff before choosing the subject: run git diff --cached --stat and git diff --cached --name-status. If amending an existing commit message, inspect git show --stat --name-status HEAD.
  • Make the subject describe the whole change set, not just one file, one subtask, or the latest edit.
  • Choose the scope from the whole change set's primary intent, not from the last file edited, a helper file, or any single path in the diff.
  • Use only literal valid scopes from AGENTS.md. Do not invent broad scopes such as tooling or infrastructure.
  • Use an imperative title.
  • Keep the subject concise.
  • Include a body when the commit changes behavior, fixes a bug, adds migration or debugging context, or needs rationale that the subject cannot carry. Do not rely on changesets, PR text, or chat context to explain why the change exists.
  • Use the body to explain the problem and why this approach was taken. Avoid merely restating the staged file list.
  • Subject-only commits are acceptable only for trivial mechanical changes where the context is obvious from the subject and diff.
  • Wrap commit body lines at 80 characters. Do this before committing or amending, and verify it afterward.
  • Add ! after the scope for breaking changes.
  • Do not add co-author lines.
  • Do not mention Codex, Claude, or any AI assistant.

Before stopping after a commit or amend, verify:

  • The subject describes the whole final diff.
  • The scope is valid, or intentionally omitted for a cross-scope change.
  • Body lines are wrapped at 80 characters.
  • Author and committer are correct.
  • The branch has the intended number of commits.

Boundaries

  • Do not run the release process. Releases are automated.
  • Do not edit changelogs manually.
  • Do not push unless the user explicitly asks.
  • A request to push with --no-verify skips the Git hook only. It does not skip the explicit formatting and verification steps above.
  • If the worktree contains unrelated changes that make staging ambiguous, stop and ask which files belong in the commit.

© foldkit, 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 in .agents/skills/commit-changes of foldkit/foldkit.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit d21db42

Compare with similar skills

Commit Changes 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 Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit Changes this skillfoldkit/foldkit918—~1.2kAutomated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost55k—~3.8kAutomated 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-skills103k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT

Similar skills

  • Migrate Internal Package into Ghost

    TryGhost/Ghost

    Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    55k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • 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.

    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

  • 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

More from foldkit/foldkit

All 18 skills in this repo

  • Foldkit

    foldkit/foldkit

    A skill your agent uses whenever working with Foldkit. An agent skill from foldkit/foldkit.

    918 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Write Release Blog Post

    foldkit/foldkit

    Outline, draft, or revise a Foldkit version release blog post using the repository's announcement style and editorial preferences.

    918 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Audit Program

    foldkit/foldkit

    Audit an existing Foldkit program against the architecture, conventions, and quality bar.

    918 GitHub stars~7.2k tokensUpdated today
    Auto-check passed

  • Generate Program

    foldkit/foldkit

    Generate a complete, idiomatic Foldkit program from a natural language description.

    918 GitHub stars~20k tokensUpdated today
    Auto-check passed

  • Changesets

    foldkit/foldkit

    Concise PR finalization changesets. An agent skill from foldkit/foldkit.

    918 GitHub stars~923 tokensUpdated today
    Auto-check passed

  • Dependency Maintenance

    foldkit/foldkit

    Dependency maintenance. An agent skill from foldkit/foldkit.

    918 GitHub stars~683 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Commit Changes

What does Commit Changes do?

Create a git commit in the Foldkit monorepo with changeset enforcement and formatting. Commit Changes is an agent skill from foldkit/foldkit. Create a git commit in the Foldkit monorepo with changeset enforcement and formatting.

When should I use Commit Changes?

Commit Changes fits situations like: the user asks Codex to commit current changes; create a changeset-backed commit; prepare a local Foldkit commit.

How do I install Commit Changes in Claude Code?

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

How do I install Commit Changes in Codex?

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

Can I use Commit Changes 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 foldkit/foldkit --skill commit-changes -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-changes, .gemini/skills/commit-changes, .github/skills/commit-changes and .opencode/skills/commit-changes in your project.

What does Commit Changes need to run?

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

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

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

About 1.2k tokens (SKILL.md is roughly 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 Changes?

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

Who maintains Commit Changes?

foldkit (a GitHub organization) maintains it in foldkit/foldkit, which has 918 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 8, 2026.

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