174 Commit 366fb3ff

Name: 174 Commit 366fb3ff
Author: tools-only

ASecurity

Create a conventional commit with auto-generated message

9 stars
0 votes
0 copies
1 view
Added October 11, 2026

toolsbashgit

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 174-commit_366fb3ff --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 174 Commit 366fb3ff?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 174 Commit 366fb3ff

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-174-commit-366fb3ff/badge)](https://www.skillsdirectory.com/skills/tools-only-174-commit-366fb3ff)

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

SKILL.md

---
allowed-tools: Bash(git status:*), Bash(git diff:*), Bash(git add:*), Bash(git commit:*)
description: Create a conventional commit with auto-generated message
argument-hint: [optional scope or message hint]
---

## Context

- Current branch: !`git branch --show-current`
- Git status: !`git status --short`
- Staged changes: !`git diff --cached --stat`
- Staged diff: !`git diff --cached`
- Recent commits (for style reference): !`git log --oneline -5`

## Task

Based on the staged changes above, create a single git commit:

1. Analyze the staged diff to understand what changed
2. Generate a conventional commit message following the format:
   - `type(scope): description`
   - Types: feat, fix, docs, style, refactor, perf, test, chore
3. If no changes are staged, inform the user and suggest staging files
4. Execute the commit

$ARGUMENTS