Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Commit

ASecurity

Commit changes to the repository.

5 stars
0 votes
0 copies
1 views
Added 10/6/2026
documentation

Works with

mcp

Security Analysis

A100/100

Scanned 10/6/2026

$npx -y skills add aaronmallen/aaronmallen.me --skill commit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Commit?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Commit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aaronmallen-commit/badge)](https://www.skillsdirectory.com/skills/aaronmallen-commit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
description: Commit changes to the repository.
name: commit
---

# Commit

The caller may name an issue, say whether this is the issue's last commit, and name a spec the commit closes. With
no issue, the commit names none.

## 1. Read the changes

Read the working change the way [`.claude/vcs.md`][vcs] describes. Work out what landed and why. If a change does
not explain itself, ask before writing the message.

## 2. Write the message

```text
<scope>: <subject>

<body>

<keywords>
```

Wrap the whole message at 72 characters.

The scope names the part of the project that changed. A change inside one slice, in `slices/<name>` or the
`lib/<name>` it owns, takes the slice name: `posts`, `admin`, `mcp`. Code outside any one slice takes one of `app`,
`assets`, `claude`, `config`, `db`, `lib`, `scripts`, `spec`, and a change that spans several slices takes `app`.

The subject names the code that landed, not what it does for a user. Write `app: add the post view and layout`,
not `app: make posts look right`. Developers read the log to find where a change went in.

The body is prose in paragraphs. Say what the change does, then say why each decision that is not obvious
went the way it did. It is not a bulleted changelog. Leave the body out only when the subject tells the whole
story.

The keywords name the issue, as [`.claude/issues.md`][issues] says under "Reference an issue". The last commit
for an issue, or its only one, ends with `Closes #<issue>`. Any commit before it ends with `See #<issue>`. When
the caller names a spec, add `Closes #<spec>` on the next line. With no issue, leave the paragraph out.

## 3. Commit

Record the change the way [`.claude/vcs.md`][vcs] describes, and pass the message you wrote without rewrapping it.

## 4. One change per commit

If the working copy holds unrelated work, split it before you describe anything. [`.claude/vcs.md`][vcs] says how.
Describe each half on its own. When the halves share an issue, only the one on top closes it, and the one
under it says `See`.

[issues]: .claude/issues.md
[vcs]: .claude/vcs.md

Attribution

aaronmallenaaronmallen
View sourceSee grades on GitHubMore from aaronmallen →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

Architecture Diagram Creator

Create comprehensive HTML architecture diagrams with data flows, business context, and system architecture.

6661 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in W...

1798860 votes
View all in documentation →