skilld
All skills
softaworks avatar

/commit-work

@1c0662a
by softaworkssoftaworks/agent-toolkit2.5k stars
230

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/softaworks/agent-toolkit/commit-work

This session only. Nothing lands on disk.

referencescommit-message-template.md

≈87 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Commit message template (Conventional Commits)

<type>(<scope>): <summary>

<What changed.>
<Why it changed.>

Notes:

  • Keep the summary imperative and specific ("Add", "Fix", "Remove", "Refactor").
  • Avoid implementation minutiae; focus on behavior and intent.
  • If breaking: use ! in header and/or add BREAKING CHANGE: footer.

Source: SKILL.md on GitHub

Third-party checks

No alerts17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    The skill is a git workflow helper that facilitates creating logically scoped and well-documented commits. It follows best practices by encouraging patch staging, thorough review of changes, and running verification tests. It includes safety checks for sensitive information like secrets and tokens. No security issues were detected.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer7mo

    3 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 1c0662a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Dormantupdated 9 months ago

Topics

  • Git/VCS
  • commits
  • conventional-commits
  • staging
  • commit-messages
  • workflow
  • patch-staging
  • code-review

README badge

README badge for softaworks/agent-toolkit/commit-work

What it does

Creates logical, reviewable git commits by staging intended changes, splitting unrelated work across multiple commits, and writing Conventional Commits messages with clear what/why descriptions. Guides the agent through inspecting diffs, deciding commit boundaries, patch-staging mixed changes, and verifying before committing.

Generated from the current SKILL.md.

Frequently asked

Does this skill require Conventional Commits?
Yes. Conventional Commits are required; the skill uses the type(scope): summary format with optional body and footer.
How does this handle mixed changes in a single file?
The skill uses patch staging (git add -p) to split unrelated changes within the same file into separate commits.
What verification does this run before committing?
The skill runs the repo's fastest meaningful check (unit tests, lint, or build) as a sanity check, but does not mandate a specific tool or test framework.
When should I use this skill—single commit or multiple?
The skill defaults to multiple small commits when changes are unrelated (e.g., feature vs refactor, backend vs frontend); single commits are used only for logically cohesive changes.

Generated from the current SKILL.md. These answers refresh after source changes.