Skip to content
Back to skills

Push Forbid

ASecurity

Disable automatic pushing. From now on, do NOT push to the remote automatically. Use when: (1) User says 'push forbid', 'no push', or 'stop pushing', (2) During sequential large development to save CI costs, (3) User wants to control when changes are pushed.

  • 12 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 8, 2026
development

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add Takazudo/claude-resources --skill push-forbid --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Push Forbid?

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

Security grade badge for Push Forbid
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/takazudo-push-forbid/badge)](https://www.skillsdirectory.com/skills/takazudo-push-forbid)

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

Download with Pro
SKILL.md
---
name: push-forbid
description: "Disable automatic pushing. From now on, do NOT push to the remote automatically. Use when: (1) User says 'push forbid', 'no push', or 'stop pushing', (2) During sequential large development to save CI costs, (3) User wants to control when changes are pushed."
---

# Push Forbid

From now on, do NOT push to the remote automatically. Even if you commit changes, never push unless I explicitly ask you to. This is typically used during sequential large development or to save CI costs.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.