How do I install the Git Pushing Hardened skill?

Run npx skillmds@latest add faberlens/git-pushing-hardened in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Pushing Hardened safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Pushing Hardened?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Pushing Hardened free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Pushing Hardened?

faberlens (@faberlens) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Pushing Hardened by faberlens — Agent Skill

Name: Git Pushing Hardened
Rating: 4.2 (5 reviews)
Author: faberlens

Git Pushing Hardened

Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.

faberlens Updated Sep 10, 2026

File contents

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.

---name: git-pushing-hardeneddescription: Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.---# Git Push WorkflowStage all changes, create a conventional commit, and push to the remote branch.## When to UseAutomatically 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:```bashbash skills/git-pushing/scripts/smart_commit.sh```With custom message:```bashbash 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.

Frequently asked questions