git-commit-writer-free
Write Conventional Commits from Staged Changes
Writing accurate conventional commits from complex staged changes takes time and can produce inconsistent results. This skill inspects staged Git changes and recommends a concise, scoped commit message.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "git-commit-writer-free" from https://skillstore.io/skills/justhandledlabs-git-commit-writer-free.md and its manifest at https://skillstore.io/api/skills/justhandledlabs-git-commit-writer-free/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 "git-commit-writer-free". Staged changes add password reset endpoints and related tests.
Expected outcome:
feat(auth): add password reset endpoints
- Adds reset request and confirmation flows
- Covers the new behavior with tests
Using "git-commit-writer-free". Staged changes rename a public API response field and update its documentation.
Expected outcome:
feat(api)!: rename account status response field
- Updates the public response contract
- Requires downstream clients to use the new field
Security Audit
SafeAll 41 static findings are false positives caused by Markdown code formatting or legitimate Git workflow instructions. The skill uses fixed local inspection commands without interpolation, network access, destructive operations, or evidence of malicious intent.
Risk Factors
⚙️ External commands (41)
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/justhandledlabs-git-commit-writer-free/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/justhandledlabs-git-commit-writer-free?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/justhandledlabs-git-commit-writer-free?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/justhandledlabs-git-commit-writer-free/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/justhandledlabs-git-commit-writer-free.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
justhandledlabs. (2026). git-commit-writer-free security audit report (audit version 1) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/justhandledlabs-git-commit-writer-free/audits/1BibTeX citation
@techreport{justhandledlabs-justhandledlabs-git-commit-writer-free-2026,
author = {justhandledlabs},
title = {git-commit-writer-free security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/justhandledlabs-git-commit-writer-free/audits/1},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "git-commit-writer-free security audit report (audit version 1)"
version: "1.0.0"
type: report
authors:
- name: "justhandledlabs"
date-released: "2026-07-22"
url: "https://skillstore.io/skills/justhandledlabs-git-commit-writer-free/audits/1"
identifiers:
- type: other
value: "skillstore:justhandledlabs-git-commit-writer-free:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Prepare a focused feature commit
Turn staged implementation and test changes into one conventional commit recommendation.
Summarize a maintenance update
Choose an accurate type and scope for staged dependency, build, or repository maintenance changes.
Flag a breaking release change
Detect evidence of public contract changes and recommend a breaking conventional commit marker.
Try These Prompts
Write a conventional commit message for my staged changes.
Review my staged changes and recommend the best commit type, scope, and summary.
Generate a commit message, explain the chosen type and scope, and provide one alternative when intent is ambiguous.
Analyze the staged diff for public API or schema breaks, then propose a breaking conventional commit with concise migration context.
Best Practices
- Stage only changes that belong in one commit before using the skill.
- Review the suggested type, scope, and breaking marker against project conventions.
- Recheck the staged diff after any change before accepting the message.
Avoid
- Do not request a message before staging changes.
- Do not mix unrelated staged work and expect one precise scope.
- Do not accept a breaking marker without public contract evidence.
Frequently Asked Questions
Does this skill create the Git commit?
Does it include unstaged changes?
Which commit format does it use?
How does it choose a scope?
How does it detect breaking changes?
What happens when nothing is staged?
Developer Details
Author
justhandledlabsLicense
MIT
Author version
v1.0.0
Skillstore revision
r1
Ref
1b458f7833f8bbcda2dfb11d8ce6f3f773c62218
Maintenance freshness
7/22/2026
Usage
0 downloads · 0 views
File structure
📄 SKILL.md