commit-work
Create Review-Ready Git Commits
Messy staging and weak messages slow code review. This skill guides selective staging, commit splitting, Conventional Commits messages, and verification.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "commit-work" from https://skillstore.io/skills/softaworks-commit-work.md and its manifest at https://skillstore.io/api/skills/softaworks-commit-work/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "commit-work". Commit this authentication bugfix.
Expected outcome:
One focused fix commit with an authentication scope, a short why-focused body, and the verification command result.
Using "commit-work". These changes include formatting, a new endpoint, and tests.
Expected outcome:
- A formatting commit for mechanical changes.
- A feature commit for the endpoint behavior.
- A test commit covering the new endpoint.
Using "commit-work". Help me prepare commits before review.
Expected outcome:
A staged-change summary, final commit messages, and a short record of checks run before handoff.
Security Audit
SafeThe static findings are Markdown command examples for normal git workflows, not executable Ruby or shell code embedded in the skill. No prompt injection, data exfiltration intent, or unsafe hidden behavior was found in the reviewed skill text.
Risk Factors
⚙️ External commands (10)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/softaworks-commit-work/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/softaworks-commit-work?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/softaworks-commit-work?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/softaworks-commit-work/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/softaworks-commit-work.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
softaworks. (2026). commit-work security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/softaworks-commit-work/audits/5BibTeX citation
@techreport{softaworks-softaworks-commit-work-2026,
author = {softaworks},
title = {commit-work security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/softaworks-commit-work/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "commit-work security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "softaworks"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/softaworks-commit-work/audits/5"
identifiers:
- type: other
value: "skillstore:softaworks-commit-work:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare a focused bugfix commit
Review changed files, stage only the bugfix, and write a concise Conventional Commits message.
Split mixed work for review
Separate refactors, tests, and feature changes into smaller commits that reviewers can evaluate independently.
Standardize repository commit history
Apply consistent message format and verification notes before sharing changes with maintainers.
Try These Prompts
Review my current changes, stage the intended work, and create a Conventional Commits message.
Inspect the working tree and split the changes into logical commits with clear summaries.
Create commits using Conventional Commits, a 72-character subject limit, and scopes from this repository.
Audit staged and unstaged changes, propose commit boundaries, run relevant checks, and report final messages.
Best Practices
- Inspect unstaged changes before adding files to the index.
- Keep each commit focused on one reviewable change.
- Run the fastest meaningful verification before finalizing a commit.
Avoid
- Stage every file without checking the diff.
- Mix formatting churn with behavior changes in one commit.
- Write messages that only describe implementation details.
Frequently Asked Questions
Does this skill require Conventional Commits?
Can it split one file across multiple commits?
Will it run tests automatically?
Does it protect against committing secrets?
Can it follow custom repository rules?
Is it only for Claude Code?
Developer Details
Author
softaworksLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
f93e9bb0daca99badb6a7e574b97737155d57cb3
Maintenance freshness
7/18/2026
Usage
7 downloads · 146 views