How do I install the Push skill?

Run npx skillmds@latest add tibursocampos/push-5 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.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Push?

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.

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

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

Push by tibursocampos — Agent Skill

Name: Push
Author: tibursocampos

File contents

STOP - Read before ANY tool call

Read E:/Source/Repos/agent-dev-toolkit/scripts/validation/fixtures/install-root/.grok/rules/guardrails.md
Read E:/Source/Repos/agent-dev-toolkit/scripts/validation/fixtures/install-root/skills/_shared/sdd-artifacts/SESSION.md; load session-state for $Cwd
If the relevant gate is not approved: STOP - ask user (pt-BR) - do NOT Write/Shell
SDD/develop skills: after ONE step/task, STOP session - handoff only
This skill body is English; user-facing prompts may be (pt-BR)

Step -1 - Gate check (report in chat before continuing)

Gate check:
[ ] guardrails.mdc read
[ ] SESSION.md read; session-state loaded
[ ] PIPELINE.md read (SDD skills only)
[ ] User confirmed current action (sim)
-> If any unchecked: STOP

Skill: push

Trigger

Use for /push, push changes, or /push.

Outcome

Current branch pushed to origin with upstream set when needed. No force-push on protected branches.

Lazy-load

When	Path (after `scripts/sync-cursor.ps1`)
Branch rules	`E:/Source/Repos/agent-dev-toolkit/scripts/validation/fixtures/install-root/rules/branch-validation.mdc`
Commit flow	`E:/Source/Repos/agent-dev-toolkit/scripts/validation/fixtures/install-root/skills/_shared/developer-common/step-4-commits-pr.md`

Process

Caveman Mode

NEVER - This skill ignores caveman_mode. Use clear prose always. Do not load CAVEMAN.md for chat compression. Commit/PR text stays normal English.

-1. Re-check guardrails and session

If missing, ask user (pt-BR):

Antes do push, confirme:
- guardrails.mdc lido
- SESSION.md carregado

Posso seguir? (sim / ajustar / cancelar)

0. Validate branch

Enforce branch-validation.mdc:

Allowed: feature/<slug>, feat/<id>
Blocked: main, master, develop, invalid patterns

If blocked, stop and show how to create a valid branch. Do not push.

1. Push

git push -u origin HEAD

Never force-push protected/default branches.

2. Report

Return branch and push status.

Must not

Push from invalid branch
Force push default branches
External work-item APIs or mandatory PR creation

Handoff

Situation	Next
Create PR (user asks)	Open PR in GitHub web UI per `step-4-commits-pr.md`
Review before PR	`/code-review`

---name: push-5description: Execute git push on the current branch after confirmation. Git-only. Use when pushing changes or invoking /push.---## STOP - Read before ANY tool call1. Read `E:/Source/Repos/agent-dev-toolkit/scripts/validation/fixtures/install-root/.grok/rules/guardrails.md`2. Read `E:/Source/Repos/agent-dev-toolkit/scripts/validation/fixtures/install-root/skills/_shared/sdd-artifacts/SESSION.md`; load session-state for `$Cwd`3. If the relevant gate is not approved: **STOP** - ask user **(pt-BR)** - do **NOT** Write/Shell4. SDD/develop skills: after **ONE** step/task, **STOP** session - handoff only5. This skill body is **English**; user-facing prompts may be **(pt-BR)**### Step -1 - Gate check (report in chat before continuing)```Gate check:[ ] guardrails.mdc read[ ] SESSION.md read; session-state loaded[ ] PIPELINE.md read (SDD skills only)[ ] User confirmed current action (sim)-> If any unchecked: STOP```---# Skill: push## TriggerUse for `/push`, `push changes`, or `/push`.## OutcomeCurrent branch pushed to `origin` with upstream set when needed. No force-push on protected branches.## Lazy-load| When | Path (after `scripts/sync-cursor.ps1`) ||------|----------------------------------------|| Branch rules | `E:/Source/Repos/agent-dev-toolkit/scripts/validation/fixtures/install-root/rules/branch-validation.mdc` || Commit flow | `E:/Source/Repos/agent-dev-toolkit/scripts/validation/fixtures/install-root/skills/_shared/developer-common/step-4-commits-pr.md` |## Process### Caveman Mode**NEVER** - This skill ignores `caveman_mode`. Use clear prose always. Do not load `CAVEMAN.md` for chat compression. Commit/PR text stays normal English.### -1. Re-check guardrails and sessionIf missing, ask user (pt-BR):```textAntes do push, confirme:- guardrails.mdc lido- SESSION.md carregadoPosso seguir? (sim / ajustar / cancelar)```### 0. Validate branchEnforce `branch-validation.mdc`:- Allowed: `feature/<slug>`, `feat/<id>`- Blocked: `main`, `master`, `develop`, invalid patternsIf blocked, stop and show how to create a valid branch. Do not push.### 1. Push```bashgit push -u origin HEAD```Never force-push protected/default branches.### 2. ReportReturn branch and push status.## Must not- Push from invalid branch- Force push default branches- External work-item APIs or mandatory PR creation## Handoff| Situation | Next ||-----------|------|| Create PR (user asks) | Open PR in GitHub web UI per `step-4-commits-pr.md` || Review before PR | `/code-review` |

Frequently asked questions

Push