Agent skill

push

Test, commit, and push in one atomic workflow. Runs Go and Python tests, commits with conventional message, pushes to current branch.

View SKILL.md on GitHub Repository
Stars 163
Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/push-boshu2-agentops

Metadata

Additional technical details for this skill

tier
execution
triggers 
[
    "push",
    "ship it",
    "commit and push",
    "push changes"
]
dependencies 
[]

SKILL.md

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

Examples

Pushing Changes

User says: /push

What happens:

  1. Runs Go and Python tests
  2. Commits with conventional message
  3. 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

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

majiayu000/claude-skill-registry

agent-ops-spec

Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-state

Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-spec

Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-testing

Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-testing

Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-state

Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.

163 31
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results