Awesome-omni-skill push

Add all changes, commit, and push to GitHub

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/push" ~/.claude/skills/diegosouzapw-awesome-omni-skill-push && rm -rf "$T"

manifest: skills/cli-automation/push/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

Add, Commit, and Push

Stage all changes, create a commit, and push to GitHub.

Steps

Run
```
git status
```
to review what will be committed. Never use the
```
-uall
```
flag.
Run
```
git diff
```
to see staged and unstaged changes.
Run
```
git log --oneline -5
```
to see recent commit message style.
Show the user the list of files that will be added/committed and ask for confirmation before proceeding. If the user declines, stop.
If
```
$ARGUMENTS
```
is provided, use it as the commit message. Otherwise, analyze the changes and generate a concise commit message that describes why the changes were made.
Stage all changes:
```
git add -A
```

Create the commit. Always end the message with the co-author line:

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

Push to the current branch:

git push origin $(git rev-parse --abbrev-ref HEAD)

If the push fails because the remote branch doesn't exist yet, push with

-u

git push -u origin $(git rev-parse --abbrev-ref HEAD)

Report the result — show the commit hash and confirm the push succeeded.

Rules

Do NOT use
```
--force
```
or
```
--no-verify
```
flags.
Do NOT commit files that look like secrets (
```
.env
```
, credentials, tokens). Warn the user if any are staged.
If there are no changes to commit, tell the user and stop.
Always use a HEREDOC to pass the commit message to avoid quoting issues.