Publishes local commits to remote branches. Ensures tests pass and uses non-destructive push methods.
Install
mkdir -p .claude/skills/push-hojinzs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18270" && unzip -o skill.zip -d .claude/skills/push-hojinzs && rm skill.zipInstalls to .claude/skills/push-hojinzs
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Publish verified local commits to the remote branch without unsafe force pushes.Key capabilities
- →Run local tests before pushing commits
- →Run linting before pushing commits
- →Push local commits to a remote branch
- →Handle non-fast-forward push rejections by fetching and merging
- →Re-run tests after a merge due to rejection
- →Verify CI status after a push
How it works
The skill executes local tests and linting, then attempts to push commits to a remote branch. If the push is rejected, it fetches, merges, re-tests, and attempts to push again.
Inputs & outputs
When to use push
- →Pushing commits to a remote feature branch
- →Handling non-fast-forward push rejections
- →Verifying CI status after a push
About this skill
/push — Git Push Workflow
Trigger
Use this skill when publishing local commits to the remote branch.
Flow
- Run local tests and lint — ensure they pass before pushing
- Push to remote:
git push origin <branch> # subsequent pushes git push -u origin <branch> # first push (sets upstream) - If push is rejected (non-fast-forward):
- Run
git fetch origin && git merge origin/main - Resolve any conflicts
- Re-run tests
- Push again
- Run
- Record push result in workpad Notes
Rules
- Never use
--force(destructive) - Only use
--force-with-leaseif absolutely necessary — record the reason in workpad - Verify CI starts after push (check GitHub Actions tab)
- Do not push directly to
mainormaster
When not to use it
- →When pushing directly to `main` or `master` branches
- →When an unsafe force push is required
- →When the user wants to bypass local tests and linting
Limitations
- →Does not allow direct pushes to `main` or `master`
- →Discourages the use of `--force`
How it compares
This workflow automates pre-push checks and handles common push rejections, providing a more controlled and safer alternative to a manual `git push`.
Compared to similar skills
push side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| push (this skill) | 0 | 4mo | Review | Beginner |
| github-workflow-automation | 11 | 2mo | Review | Advanced |
| testing-workflow | 16 | 9mo | Review | Intermediate |
| github-actions-templates | 7 | 3mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by hojinzs
View all by hojinzs →You might also like
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
github-actions-templates
wshobson
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
glab
NikiforovAll
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
create-pr
n8n-io
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
gh-fix-ci
openai
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.