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.

SKILL.md

≈70 tokens always: the name and description. ≈544 when used: this file. ≈1.3k more on demand in 2 files.

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)

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.