Index of every page on this site: llms.txt
All skills
softaworks avatar

/commit-work

@3027f20
by softaworkssoftaworks/agent-toolkit2.7k stars
254
Run it yourself

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.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

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

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈281 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    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.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    3 files scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

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

Last checked against GitHub last month.

Dormantupdated 10 months ago
  • Git/VCS
  • commits
  • conventional-commits
  • staging
  • commit-messages
  • workflow
  • patch-staging
  • code-review

README badge

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

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.

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.