Awesome-omni-skill commit

Create a git commit with a well-formatted message. Use after completing changes that should be committed.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/cli-automation/commit-milosptr" ~/.claude/skills/diegosouzapw-awesome-omni-skill-commit-c19d38 && rm -rf "$T"

manifest: skills/cli-automation/commit-milosptr/SKILL.md

safety · automated scan (low risk)

This is a pattern-based risk scan, not a security review. Our crawler flagged:

references .env files

Always read a skill's source content before installing. Patterns alone don't mean the skill is malicious — but they warrant attention.

source content

Git Commit

Create a git commit for the current changes.

Commit Message Format

Use conventional commit style:

<type>: <short description>

<optional body with more details>

Co-Authored-By: Claude <noreply@anthropic.com>

Types

```
feat
```
: New feature
```
fix
```
: Bug fix
```
refactor
```
: Code refactoring
```
style
```
: Formatting, missing semicolons, etc.
```
docs
```
: Documentation changes
```
test
```
: Adding or updating tests
```
chore
```
: Maintenance tasks

Examples

feat: add warehouse status recalculation endpoint

fix: correct working day calculation for early morning hours

refactor: extract invoice creation logic to service class

test: add feature tests for OrderController

Steps

Run
```
git status
```
to see all changes
Run
```
git diff
```
to review staged and unstaged changes
Run
```
git log --oneline -5
```
to see recent commit style
Stage relevant files with
```
git add <files>
```
(prefer specific files over
```
git add .
```
)
Create commit with descriptive message using HEREDOC format:

git commit -m "$(cat <<'EOF'
<type>: <description>

<optional details>

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

Run
```
git status
```
to verify commit succeeded

Important Notes

Do NOT commit
```
.env
```
or other sensitive files
Do NOT use
```
--amend
```
unless explicitly requested (creates new commits)
Do NOT use
```
--no-verify
```
unless explicitly requested
Do NOT push unless explicitly requested
If pre-commit hooks fail, fix issues and create NEW commit

User's hint for this commit

$ARGUMENTS