push
Commit and push to the current branch. Use --fixup to also wait for CI/CodeRabbit and fix issues.
Best use case
push is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Commit and push to the current branch. Use --fixup to also wait for CI/CodeRabbit and fix issues.
Teams using push should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/push/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How push Compares
| Feature / Agent | push | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Commit and push to the current branch. Use --fixup to also wait for CI/CodeRabbit and fix issues.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Push ## Available skills - **`/commit`** — Stage and commit changes using Conventional Commits. Runs `/verify` internally. - **`/pr-fixup`** — Wait for CI checks and CodeRabbit review, fix any failures, and push again. ## Context - Current branch: !`git branch --show-current` - Current git status: !`git status` ## Options - `--fixup` — after pushing, run `/pr-fixup` to wait for CI and CodeRabbit review, fix issues, and push again. > **Note:** This skill only uses `git push`. GitHub CLI dependency is indirect via `/pr-fixup`. ## Your task Commit any pending changes and push to the remote branch. ### Steps **Create a todo/task for each step below and mark them as completed as you go.** 1. **Uncommitted changes:** If there are dirty or staged changes, run `/commit` first (it runs `/verify` internally). 2. **Safety check:** Verify the current branch is NOT `main` or `master`. If it is, stop and ask the user — direct pushes to the default branch should go through a PR. 3. **Push** the current branch: ```bash git push ``` If the branch has no upstream, use `git push -u origin <branch>`. 4. **Report** the pushed commit hash and branch. 5. **If `--fixup`:** Run `/pr-fixup` to wait for CI checks and CodeRabbit review, fix any failures or valid comments, and push.
Related Skills
verify
Run format, typecheck, test, and lint across the monorepo. Use after implementing changes.
tdd
Implement changes using Test-Driven Development (Red-Green-Refactor). Use for bug fixes, new features, or any code change that should have test coverage.
spec
Write a feature spec — the "what & why" of a kandev product feature, before coding. Use when the user says "let's spec X" or starts a new product feature.
simplify
Simplify recently changed code — inline one-off abstractions, remove speculative code, reduce nesting, replace cleverness with clarity. Run after implementing a feature.
record
Record an architectural decision (ADR) or save an implementation plan. Use after making significant design choices or completing features.
qa
Verify a feature works after implementation. Actively try to break it — edge cases, error paths, integration wiring, and real usage flows.
pr
Commit, push, and create a PR. Default is ready-for-review with auto-fixup. Use --draft to skip review/fixup.
pr-fixup
Wait for CI checks and automated reviews (CodeRabbit, Greptile, Claude) on a PR, fix failures and address comments, then push.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
fix
Fix bugs and issues — reproduce, find root cause, minimal fix with regression test. Use when something is broken.
feature
Guided feature development — brainstorm, explore codebase, design architecture, implement with TDD, and review. Use for new features or significant changes.
e2e
Write and run web E2E tests (Playwright) using TDD — locations, patterns, commands, and debugging.