managing-commits
Manage Git Commits with Issue Context
Inconsistent commit messages make review, changelogs, and automation harder. This skill helps Claude, Codex, and Claude Code create, review, and validate Conventional Commits with GitHub issue context.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "managing-commits" from https://skillstore.io/skills/c0ntr0lledcha0s-managing-commits.md and its manifest at https://skillstore.io/api/skills/c0ntr0lledcha0s-managing-commits/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 "managing-commits". Help me write a commit message for staged auth changes.
Expected outcome:
A suggested Conventional Commit with type, scope, short subject, explanatory body, and an optional Closes footer.
Using "managing-commits". Review my recent commits before I open a pull request.
Expected outcome:
- A compliance summary for recent commit subjects.
- Specific suggestions for vague messages, missing issue references, and oversized commits.
- Recommended fixes before review.
Using "managing-commits". Group my changed files into atomic commits.
Expected outcome:
A set of logical commit groups with proposed scopes and user-editable commit messages.
Security Audit
Medium RiskMost static findings are false positives caused by Markdown examples or expected git and GitHub CLI subprocess calls without shell interpolation. One real filesystem issue remains: a predictable /tmp commit-message file can be replaced or clobbered, and the issue cache stores GitHub issue body previews locally.
Confirmed security concerns (1)
Capability review items (3)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (50)
📁 Filesystem access (9)
🌐 Network access (1)
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/c0ntr0lledcha0s-managing-commits/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/c0ntr0lledcha0s-managing-commits?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/c0ntr0lledcha0s-managing-commits?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/c0ntr0lledcha0s-managing-commits/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/c0ntr0lledcha0s-managing-commits.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
C0ntr0lledCha0s. (2026). managing-commits security audit report (audit version 10) [Author version 1.2.0]. Skillstore. https://skillstore.io/skills/c0ntr0lledcha0s-managing-commits/audits/10BibTeX citation
@techreport{c0ntr0lledcha0s-c0ntr0lledcha0s-managing-commits-2026,
author = {C0ntr0lledCha0s},
title = {managing-commits security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/c0ntr0lledcha0s-managing-commits/audits/10},
note = {Author version 1.2.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "managing-commits security audit report (audit version 10)"
version: "1.2.0"
type: report
authors:
- name: "C0ntr0lledCha0s"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/c0ntr0lledcha0s-managing-commits/audits/10"
identifiers:
- type: other
value: "skillstore:c0ntr0lledcha0s-managing-commits:audit:10"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Write a clear commit message
Generate a concise Conventional Commit message from staged changes and add issue references when appropriate.
Review branch history before a pull request
Check recent commits for format problems, vague subjects, large changes, and missing issue links.
Standardize team release notes
Apply consistent commit types and breaking-change footers so changelog automation has reliable input.
Try These Prompts
Help me write a Conventional Commit message for my staged changes.
Review the commits on my current branch for Conventional Commit format, clarity, and issue references.
Analyze my changed files and suggest logical commit groups with commit messages for each group.
Audit my branch history for changelog quality, breaking-change notation, issue references, and commits that should be squashed.
Best Practices
- Stage only one logical change before asking for a final commit message.
- Review generated issue footers before committing, especially Closes references.
- Use breaking-change footers when a change requires user migration.
Avoid
- Do not use generated commit text without checking the diff yourself.
- Do not close issues from a commit unless the change fully resolves them.
- Do not combine unrelated feature, fix, test, and documentation changes in one commit.
Frequently Asked Questions
Does this skill create commits automatically?
Does it require Conventional Commits?
Can it link commits to GitHub issues?
Can it analyze commit history?
Does it send data to GitHub?
Is it useful for teams?
Developer Details
Author
C0ntr0lledCha0sLicense
MIT
Author version
v1.2.0
Skillstore revision
r1
Ref
7db9b9f06e0ab79c575b58bc48c4d8dc9849f424
Maintenance freshness
7/18/2026
Usage
20 downloads · 295 views
File structure