push
Test, commit, and push in one atomic workflow. Runs Go and Python tests, commits with conventional message, pushes to current branch.
Best use case
push is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Test, commit, and push in one atomic workflow. Runs Go and Python tests, commits with conventional message, pushes to current branch.
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?
Test, commit, and push in one atomic workflow. Runs Go and Python tests, commits with conventional message, pushes to current branch.
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 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:** ```bash cd cli && go vet ./... cd cli && go test ./... -count=1 -short ``` **Python projects:** ```bash python -m pytest --tb=short -q ``` **Shell scripts (if shellcheck available):** ```bash shellcheck <modified .sh files> ``` If ANY test fails: **STOP.** Fix the failures before continuing. Do not commit broken code. ### Step 3: Stage Changes ```bash 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 ```bash git commit -m "<message>" ``` ### Step 6: Sync with Remote ```bash git pull --rebase origin $(git branch --show-current) ``` If rebase conflicts occur: resolve them, re-run tests, then continue. ### Step 7: Push ```bash 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 - Do NOT run `ao codex stop` after the remote push. If session closeout is needed, finish it through `$validation`, `$post-mortem`, or `$handoff` before entering `$push` ## Local Resources ### scripts/ - `scripts/validate.sh`
Related Skills
vibe
Comprehensive code validation. Runs complexity analysis then multi-model council. Answer: Is this code ready to ship? Triggers: "vibe", "validate code", "check code", "review code", "code quality", "is this ready".
validation
Full validation phase orchestrator. Vibe + post-mortem + retro + forge. Reviews implementation quality, extracts learnings, feeds the knowledge flywheel. Triggers: "validation", "validate", "validate work", "review and learn", "validation phase", "post-implementation review".
update
Reinstall all AgentOps skills globally from the latest source. Triggers: "update skills", "reinstall skills", "sync skills".
trace
Trace design decisions and concepts through session history, handoffs, and git. Triggers: "trace decision", "how did we decide", "where did this come from", "design provenance", "decision history".
test
Test generation, coverage analysis, and TDD workflow. Triggers: "test", "generate tests", "test coverage", "write tests", "tdd", "add tests", "test strategy", "missing tests", "coverage gaps".
status
Single-screen dashboard showing current work, recent validations, flywheel health, and suggested next action. Triggers: "status", "dashboard", "what am I working on", "where was I".
standards
Language-specific coding standards and validation rules. Provides Python, Go, Rust, TypeScript, Shell, YAML, JSON, and Markdown standards. Auto-loaded by $vibe, $implement, $doc, $bug-hunt, $complexity based on file types.
shared
Shared reference documents for multi-agent skills (not directly invocable)
security
Continuous repository security scanning and release gating. Triggers: "security scan", "security audit", "pre-release security", "run scanners", "check vulnerabilities".
security-suite
Composable security suite for binary and prompt-surface assurance, static analysis, dynamic tracing, repo-native redteam scans, contract capture, baseline drift, and policy gating. Triggers: "binary security", "reverse engineer binary", "black-box binary test", "behavioral trace", "baseline diff", "prompt redteam", "security suite".
scenario
Author and manage holdout scenarios for behavioral validation. Scenarios are stored in .agents/holdout/ where implementing agents cannot see them. Triggers: "$scenario", "holdout", "behavioral scenario", "create scenario", "list scenarios".
scaffold
Project scaffolding, component generation, and boilerplate setup. Triggers: "scaffold", "new project", "init project", "create project", "generate component", "setup project", "starter", "boilerplate".