How do I install the Push skill?

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

SkillMD's automated safety review verdict for this skill is CAUTION. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only, makes network calls, reads secrets. 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.

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

Push by majiayu000 — Agent Skill

File contents

Push Skill

Atomic test-commit-push workflow. Catches failures before they reach the remote.

Steps

Step 1: Detect Project Type

Determine which test suites apply:

Go: Check for go.mod (or cli/go.mod). If found, Go tests apply.
Python: Check for requirements.txt, pyproject.toml, or setup.py. If found, Python tests apply.
Shell: Check for modified .sh files. If found, shellcheck applies (if installed).

Step 2: Run Tests

Run ALL applicable test suites. Do NOT skip any.

Go projects:

cd cli && go vet ./...
cd cli && go test ./... -count=1 -short

Python projects:

python -m pytest --tb=short -q

Shell scripts (if shellcheck available):

shellcheck <modified .sh files>

If ANY test fails: STOP. Fix the failures before continuing. Do not commit broken code.

Step 3: Stage Changes

git add <specific files>

Stage only the files relevant to the current work. Do NOT use git add -A unless the user explicitly requests it. Review untracked files and skip anything that looks like secrets, temp files, or build artifacts.

Step 4: Write Commit Message

Write a conventional commit message based on the diff:

Use conventional commit format: type(scope): description
Types: feat, fix, refactor, docs, test, chore, style, perf
Keep subject line under 72 characters
Focus on WHY, not WHAT

Step 5: Commit

git commit -m "<message>"

Step 6: Sync with Remote

git pull --rebase origin $(git branch --show-current)

If rebase conflicts occur: resolve them, re-run tests, then continue.

Step 7: Push

git push origin $(git branch --show-current)

Step 8: Report

Output a summary:

Files changed count
Tests passed (with suite names)
Commit hash
Branch pushed to

Guardrails

NEVER push to main or master without explicit user confirmation
NEVER stage files matching: .env*, *credentials*, *secret*, *.key, *.pem
If tests were not run (no test suite found), WARN the user before committing
If git pull --rebase fails, do NOT force push — ask the user

Examples

Pushing Changes

User says: /push

What happens:

Runs Go and Python tests
Commits with conventional message
Pushes to current branch

Result: Verified, committed, and pushed changes in one atomic workflow.

Troubleshooting

Problem	Cause	Fix
Tests fail	Code has errors	Fix failing tests before retrying
Push rejected	Remote has new commits	Pull and rebase, then retry
No changes to commit	Working tree is clean	Make changes first

Reference Documents

references/push.feature — Executable spec: detect project type, run tests first, block push on failure, commit+push on green (soc-qk4b)

---name: pushdescription: Runs project tests, stages and commits changes with a conventional message, then rebases and pushes to the current branch, stopping on any failure.---# Push SkillAtomic test-commit-push workflow. Catches failures before they reach the remote.## Steps### Step 1: Detect Project TypeDetermine which test suites apply:- **Go:** Check for `go.mod` (or `cli/go.mod`). If found, Go tests apply.- **Python:** Check for `requirements.txt`, `pyproject.toml`, or `setup.py`. If found, Python tests apply.- **Shell:** Check for modified `.sh` files. If found, shellcheck applies (if installed).### Step 2: Run TestsRun ALL applicable test suites. Do NOT skip any.**Go projects:**```bashcd cli && go vet ./...cd cli && go test ./... -count=1 -short```**Python projects:**```bashpython -m pytest --tb=short -q```**Shell scripts (if shellcheck available):**```bashshellcheck <modified .sh files>```If ANY test fails: **STOP.** Fix the failures before continuing. Do not commit broken code.### Step 3: Stage Changes```bashgit add <specific files>```Stage only the files relevant to the current work. Do NOT use `git add -A` unless the user explicitly requests it. Review untracked files and skip anything that looks like secrets, temp files, or build artifacts.### Step 4: Write Commit MessageWrite a conventional commit message based on the diff:- Use conventional commit format: `type(scope): description`- Types: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `style`, `perf`- Keep subject line under 72 characters- Focus on WHY, not WHAT### Step 5: Commit```bashgit commit -m "<message>"```### Step 6: Sync with Remote```bashgit pull --rebase origin $(git branch --show-current)```If rebase conflicts occur: resolve them, re-run tests, then continue.### Step 7: Push```bashgit push origin $(git branch --show-current)```### Step 8: ReportOutput a summary:- Files changed count- Tests passed (with suite names)- Commit hash- Branch pushed to## Guardrails- NEVER push to `main` or `master` without explicit user confirmation- NEVER stage files matching: `.env*`, `*credentials*`, `*secret*`, `*.key`, `*.pem`- If tests were not run (no test suite found), WARN the user before committing- If `git pull --rebase` fails, do NOT force push — ask the user## Examples### Pushing Changes**User says:** `/push`**What happens:**1. Runs Go and Python tests2. Commits with conventional message3. Pushes to current branch**Result:** Verified, committed, and pushed changes in one atomic workflow.## Troubleshooting| Problem | Cause | Fix ||---------|-------|-----|| Tests fail | Code has errors | Fix failing tests before retrying || Push rejected | Remote has new commits | Pull and rebase, then retry || No changes to commit | Working tree is clean | Make changes first |## Reference Documents- [references/push.feature](references/push.feature) — Executable spec: detect project type, run tests first, block push on failure, commit+push on green (soc-qk4b)

Frequently asked questions

Push