agentsclimarketplace
Sign in

Push

Skill lklimek/claudius/skills/push

Commit, push, and create PR. Auto-creates feature branch if on base. Use when user wants to commit and push, create a PR, ship work, send changes upstream, open a pull request, or publish a branch.From its SKILL.md

Install
npx -y skills add lklimek/claudius --skill push

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • skips confirmationTells the agent to proceed without asking first, 2 times: "No push confirmation needed — user explicitly invoked /push, intent is clear" and 1 more.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 1 command, including `git remote show origin`.

SKILL.md

2.4 KB, 506 tokens by cl100k_base, as published. Nobody here has run it

Push

Prerequisites

Load claudius:git-and-github skill first — all commit, push, PR, and attribution conventions come from there.

Steps

  1. Ensure feature branch

    • Base branch: read from gitStatus context (Main branch: ...). Fallback: git remote show origin
    • If ON the base branch: fetch, create a feature branch (feat/..., fix/..., chore/... from context), switch to it

  2. Version bump (if applicable)

    • Check project's CLAUDE.md for versioning policy (SemVer, changelog, version file locations)
    • If policy exists, this PR MUST carry a version bump before it's considered done — bump version and update changelog before committing (or before marking the PR ready, if bumping later once full scope is known).
    • Exactly once per unmerged PR, not per commit: if this branch already carries a version bump from an earlier commit and hasn't merged yet, don't bump again — amend the existing changelog entry instead. Re-bump only if the change's SemVer category grows (e.g. patch → minor). Never conclude "not merged yet" or "already bumped once elsewhere" means the bump can be skipped for this PR itself.
    • Same reasoning covers backward compatibility: nothing in an unmerged PR is released yet, so its own earlier commits don't constrain later ones on the same branch.

  3. Stage and commit

    • Review changes, check for secrets — warn and exclude if found
    • Stage and commit per git-and-github conventions

  4. Push to remote

  5. PR

    • PR body MUST follow the TL;DR → User story → Scenario → Detailed discussion skeleton per git-and-github §Creating a PR
    • If PR exists for this branch: update its title and description to reflect current changes
    • If no PR: create a draft PR with summary + test plan per git-and-github

Notes

  • No push confirmation needed — user explicitly invoked /push, intent is clear
  • This overrides the "ask before push" rule from git-and-github for this invocation only
  • After completing, do NOT push again without a new explicit /push or user request — one invocation = one push

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.