How do I install the Commit skill?

Run npx skillmds@latest add toy-crane/commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit?

toy-crane (@toy-crane) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit by toy-crane — Agent Skill

Name: Commit
Author: toy-crane

Commit

Create Git commits for the current request's in-scope changes as logical Conventional Commits. Always use this skill for an actual Git commit operation, including requests to commit or amend changes, save work in repository history, stage and record selected files, or group staged or unstaged changes into commits. Use it even when the request describes recording changes without saying "commit"; it performs the commit rather than only suggesting a message, and it does not push.

toy-crane 09d795d 6 files · 7.6 KB Updated Sep 17, 2026

File contents

Commit changes

Commit the changes owned by the current request. Treat explicit invocation as authorization to create commits, while leaving the remote untouched.

Understand the current status, diff, and recent commit style before staging. Separate unrelated concerns into commits that can be understood, reverted, or cherry-picked independently; keep a behavior and the tests that establish it together when they form one change.

Preserve work outside the request. Leave pre-existing or ambiguously owned changes unstaged and ask only when their ownership prevents a safe commit. Exclude credentials, secrets, private keys, and environment files unless the user explicitly establishes that a particular file is safe and intended for version control.

Use Conventional Commit messages that describe the actual diff and fit the repository's history. Honor repository hooks and repair failures caused by the current change; a failed hook is evidence to address, not a check to bypass.

Finish when every in-scope change is committed, every remaining working-tree change is accounted for, and the user has the resulting commit hashes and subjects. If there is nothing to commit, report that state without creating an empty commit.

Frequently asked questions