Skip to content
Back to skills

Commit

ASecurity

Commit current work with optional message. Handles git status/diff checking and message formatting.

  • 13 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 10, 2026
toolsgit

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add yulonglin/dotfiles --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 with every re-scan.

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

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

Download with Pro
SKILL.md
---
name: commit
description: Commit current work with optional message. Handles git status/diff checking and message formatting.
---

# Commit current work

## Instructions

1. **Check Status**: Run the following commands to understand the current state:
   - `git status --short`
   - `git diff --stat`
   - `git log --oneline -3`

2. **Analyze Changes**:
   - Review the output to understand what has changed.
   - If `git diff` doesn't provide enough info (e.g., new files), read the files or use your working memory.
   - Determine if the work should be split into multiple logical commits.

3. **Stage Changes**:
   - New/modified files: `git add <file1> <file2> ...`
   - Deleted files: `git add -u <path>` (plain `git add` fails on paths no longer on disk)
   - Mixed (new + deleted): combine both commands, or use `git add -u` for deletions then `git add` for new files

4. **Commit**:
   - For each logical change, write a commit message in the following format:
     - Short title description (< 80 characters)
     - 2~3 bullet points (< 80 characters) with a quick description
   - Use `git commit -m "..."` to commit the changes.

## Important Notes
- Prepend `GIT_EDITOR=true` to all git commands you run, especially the ones looking at diffs, to avoid blocking.
- If you're at the start of the session, use subagents to summarize changes made by others if needed.
- Only commit work when instructed or when a task is complete.

Optional: Ask me if I would like to push the commit.

Attribution

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

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.