agentmods.dev

push

push is a skill for Claude Code from StephenQiu30/stephen-claude. It costs 31 tokens per session (1,112 once invoked), scanned A, a copy of push, MIT.

A procedure for sending the current Git branch to the shared repository and creating or updating its GitHub pull request, a proposed code change for review.

In plain words
What is it for?
Use it when asked to push changes, open a pull request, update an existing one, or recover from a rejected push.
Why use it?
It checks branch history, commit formats, authentication, and validation before publishing changes.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

not rated 2repo 3mo ago A scan 31 tokens copy · 86% MIT

Good fit Use it when asked to push changes, open a pull request, update an existing one, or recover from a rejected push.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stephenqiu30/stephen-claude/push
View source ↗ StephenQiu30/stephen-claude
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add StephenQiu30/stephen-claude --skill push
Clone the repo
git clone --depth 1 https://github.com/StephenQiu30/stephen-claude

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for push

README.md
[![agentmods](https://agentmods.dev/badge/skills/stephenqiu30/stephen-claude/push/github.svg)](https://agentmods.dev/skills/stephenqiu30/stephen-claude/push)
Your own site
<a href="https://agentmods.dev/skills/stephenqiu30/stephen-claude/push"><img src="https://agentmods.dev/badge/skills/stephenqiu30/stephen-claude/push/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for push

Your own site · 80×15
<a href="https://agentmods.dev/skills/stephenqiu30/stephen-claude/push"><img src="https://agentmods.dev/badge/skills/stephenqiu30/stephen-claude/push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,112 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.01112
Opus 5.5 $0.00012 $0.00445
Sonnet 5.5 $0.00006 $0.00222
Haiku 4.5 $0.00003 $0.00111

Measured 1mo ago against content hash 5b165ef6671c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

push scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

86% identical to push — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/push/SKILL.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Push

Prerequisites

  • gh CLI is installed and available in PATH.
  • gh auth status succeeds for GitHub operations in this repo.

Goals

  • Push current branch changes to origin safely.
  • Create a PR if none exists for the branch, otherwise update the existing PR.
  • Keep branch history clean when remote has moved.
  • pull: use this when push is rejected or sync is not clean (non-fast-forward, merge conflict risk, or stale branch).

Steps

  1. Identify current branch and confirm remote state.

  2. Confirm branch commits use only allowed types (test:, docs:, impl:, chore:, feat:, refactor:) with test-first ordering for behavior work.

  3. Run project validation for the change scope before pushing.

  4. Push branch to origin with upstream tracking if needed, using whatever remote URL is already configured.

  5. If push is not clean/rejected:

    • If the failure is a non-fast-forward or sync problem, run the pull skill to merge origin/main, resolve conflicts, and rerun validation.
    • Push again; use --force-with-lease only when history was rewritten.
    • If the failure is due to auth, permissions, or workflow restrictions on the configured remote, stop and surface the exact error instead of rewriting remotes or switching protocols as a workaround.

  6. Ensure a PR exists for the branch:

    • If no PR exists, create one.
    • If a PR exists and is open, update it.
    • If branch is tied to a closed/merged PR, create a new branch + PR.
    • Write a proper PR title that clearly describes the change outcome
    • For branch updates, explicitly reconsider whether current PR title still matches the latest scope; update it if it no longer does.

  7. Write/update PR body using .github/pull_request_template.md and WORKFLOW.md PR submission content (Test-First required):

    • Fill every section with concrete content for this change.
    • Include Test-first Evidence, Tests added, Commands run, Result, Agent Usage, and Reviewer Checklist.
    • Replace all placeholder comments (<!-- ... -->).
    • Keep bullets/checkboxes where template expects them.
    • If PR already exists, refresh body content so it reflects the total PR scope (all intended work on the branch), not just the newest commits, including newly added work, removed work, or changed approach.
    • Do not reuse stale description text from earlier iterations.

  8. Reply with the PR URL from gh pr view.

Read the full file on GitHub · 122 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 122 lines · 31 tokens per session scan A 5b165ef6671c

Subscribe to this mod's changes

push is a skill published in the GitHub repository StephenQiu30/stephen-claude (2 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 1,112 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to push, differing in 16 lines, and is treated as a copy.

Git and workflowagent-workflowsai-agentsclaudegithub-actionssmartsymphony
Related

Other skills, from other repositories

changelog-scan

Scan merged PRs and commits since a given reference, extract titles, labels, types, and signals. Produces structured input for release notes drafting.

cobusgreyling/loop-engineering · 35 tokens

draft-release-notes

Turn changelog-scan output into polished, categorized release notes draft. Propose only.

cobusgreyling/loop-engineering · 23 tokens

github-workflow-automation

Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.

ruvnet/ruflo · 26 tokens

deploy-python-project

Validate and deploy this generated Python project using its selected target, portable Docker base, and optional Pulumi or Terraform configuration. Use for deployment preparation, local container checks, cloud previews, release rollout, health verification, or deployment troubleshooting.

leynier/python-template · 50 tokens

cpv-setup-marketplace-auto-notification

Use when configuring a plugin to notify its marketplace after each release so Claude Code can auto-update users. Universal CI recipe for any plugin/marketplace pair. Used dynamically via cpv-the-skills-menu (TRDD-478d9687).

Emasoft/claude-plugins-validation · 59 tokens

github-workflow-automation

Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.

ruvnet/agentic-flow · 26 tokens