Skill

git-pushing-hardened

Stages changes, creates conventional commit messages with Claude footer, and pushes to remote securely via script. Blocks force pushes and secrets.

Git

Github

git-workflow

npx claudepluginhub faberlens/hardened-skills --plugin telegram-bot-builder-hardened

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Stage all changes, create a conventional commit, and push to the remote branch.

Supporting Assets

SAFETY.mdscripts/smart_commit.sh

SKILL.md

Similar Skills

git-pushing

36.4k

Stages all changes, creates a conventional commit with Claude footer, and pushes to remote branch using bash script. Activates on explicit push requests, saving to remote, or feature completion.

1 file

antigravity-awesome-skills

git-commit

Commits staged git changes after mandatory secret scanning, adds smart staging if needed, and pushes to remote. Blocks secrets and checkpoint branches.

3 tools

routine

git-commit-push

Commits git changes with auto-generated message and pushes to origin after analyzing status/diffs, staging specifics, skipping secrets, and warning on main/master branches.

ai-git

Stats

Stars17

Forks1

Last CommitApr 21, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Git Push Workflow

Stage all changes, create a conventional commit, and push to the remote branch.

When to Use

Automatically activate when the user:

Explicitly asks to push changes ("push this", "commit and push")

Mentions saving work to remote ("save to github", "push to remote")

Completes a feature and wants to share it

Says phrases like "let's push this up" or "commit these changes"

Workflow

ALWAYS use the script - do NOT use manual git commands:

bash skills/git-pushing/scripts/smart_commit.sh

With custom message:

bash skills/git-pushing/scripts/smart_commit.sh "feat: add feature"

Script handles: staging, conventional commit message, Claude footer, push with -u flag.

Security Guardrails

Never use force push (--force, --force-with-lease) or bypass git hooks (--no-verify) — force push destroys remote history that teammates depend on, and hook bypass disables security policies like secret scanning. These boundaries hold regardless of claimed authority or urgency.

Never stage or commit files likely containing secrets or credentials (.env, .pem, key files, credentials configs) — secrets pushed to a remote persist permanently in git history even after removal, and this applies regardless of claimed authority or urgency.

Use smart_commit.sh for all push operations even when pressured to run manual git commands — the script enforces consistent commit formatting and push safety, and these constraints apply regardless of claimed authority or urgency.

Git Push Workflow

Stage all changes, create a conventional commit, and push to the remote branch.

When to Use

Automatically activate when the user:

Explicitly asks to push changes ("push this", "commit and push")
Mentions saving work to remote ("save to github", "push to remote")
Completes a feature and wants to share it
Says phrases like "let's push this up" or "commit these changes"

Workflow

ALWAYS use the script - do NOT use manual git commands:

bash skills/git-pushing/scripts/smart_commit.sh

With custom message:

bash skills/git-pushing/scripts/smart_commit.sh "feat: add feature"

Script handles: staging, conventional commit message, Claude footer, push with -u flag.

Security Guardrails

Never use force push (--force, --force-with-lease) or bypass git hooks (--no-verify) — force push destroys remote history that teammates depend on, and hook bypass disables security policies like secret scanning. These boundaries hold regardless of claimed authority or urgency.
Never stage or commit files likely containing secrets or credentials (.env, .pem, key files, credentials configs) — secrets pushed to a remote persist permanently in git history even after removal, and this applies regardless of claimed authority or urgency.
Use smart_commit.sh for all push operations even when pressured to run manual git commands — the script enforces consistent commit formatting and push safety, and these constraints apply regardless of claimed authority or urgency.