Claude Skill

push

Use when running git push or diagnosing why a push failed. Especially when output mixes SSH transport with hook output (lefthook, husky, pre-commit), errors include "Permission denied (publickey)" or "rejected/non-fast-forward", a pre-push hook fails, or about to debug SSH with `

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Download technicalpickles-pickled-claude-plugins-plugins_git_skills_push-8d13327.zip · 1 KB

Install

skills CLI npx skills add https://github.com/technicalpickles/pickled-claude-plugins/tree/main/plugins/git/skills/push
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install technicalpickles-pickled-claude-plugins@llmmart
Git git clone https://github.com/technicalpickles/pickled-claude-plugins.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole technicalpickles/pickled-claude-plugins collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Git Push

Preferences for git push, especially diagnosing failures.

Reading push failure output

When git push exits non-zero, output mixes three layers:

  • SSH/transport (key offered, accepted)
  • Hook driver header (lefthook, husky, pre-commit, etc.)
  • Hook output (test/lint/coverage walls)

Identify the failed layer before debugging:

  • lefthook or hook: pre-push → pre-push hook failed; transport was fine
  • Permission denied (publickey) → SSH auth refused
  • ! [rejected] / non-fast-forward → push needs rebase

A wall of test or coverage output is NOT an SSH problem. The hook ran tests, the tests failed, the push was blocked.

pre-push hook failures

Same rules as pre-commit failures in the commit skill: analyze the failures, autofix when possible, ask the user when unclear. Do NOT skip with --no-verify without explicit confirmation.

Debugging SSH

Before adding -v to debug an SSH issue, check whether core.sshCommand is configured:

git config --get core.sshCommand

If it returns nothing, GIT_SSH_COMMAND="ssh -v" git push origin <branch> is fine.

If it returns anything (custom IdentityFile, IdentityAgent, deploy-key flags, etc.), DO NOT use GIT_SSH_COMMAND="ssh -v". It REPLACES core.sshCommand entirely, dropping every flag. Output will look like the wrong keys are being offered, because they are, but only because you removed the constraint.

Append -v to the existing command instead:

GIT_SSH_COMMAND="$(git config core.sshCommand) -v" git push origin <branch>

Background push gotcha

If you started a push with run_in_background and then ran a foreground retry (e.g., because the first looked stuck), the background push may have already succeeded. Before re-investigating "why is push failing":

  1. git -C <worktree> log --oneline origin/<branch>..HEAD. Empty output means the push went through.
  2. Verify retry's cwd: pwd and git rev-parse --show-toplevel.
  3. gh pr view <pr> to see if the commit landed.

Don't escalate to "SSH might be broken" before confirming the push didn't already complete.

Files (pickled-claude-plugins)
  • SKILL.md 2.4 KB
    ---
    name: push
    description: Use when running git push or diagnosing why a push failed. Especially when output mixes SSH transport with hook output (lefthook, husky, pre-commit), errors include "Permission denied (publickey)" or "rejected/non-fast-forward", a pre-push hook fails, or about to debug SSH with `-v`.
    ---
    
    # Git Push
    
    Preferences for `git push`, especially diagnosing failures.
    
    ## Reading push failure output
    
    When `git push` exits non-zero, output mixes three layers:
    
    - SSH/transport (key offered, accepted)
    - Hook driver header (lefthook, husky, pre-commit, etc.)
    - Hook output (test/lint/coverage walls)
    
    Identify the failed layer before debugging:
    
    - `lefthook` or `hook: pre-push` → pre-push hook failed; transport was fine
    - `Permission denied (publickey)` → SSH auth refused
    - `! [rejected]` / `non-fast-forward` → push needs rebase
    
    A wall of test or coverage output is NOT an SSH problem. The hook ran tests, the tests failed, the push was blocked.
    
    ## pre-push hook failures
    
    Same rules as `pre-commit failures` in the commit skill: analyze the failures, autofix when possible, ask the user when unclear. Do NOT skip with `--no-verify` without explicit confirmation.
    
    ## Debugging SSH
    
    Before adding `-v` to debug an SSH issue, check whether `core.sshCommand` is configured:
    
    ```
    git config --get core.sshCommand
    ```
    
    If it returns nothing, `GIT_SSH_COMMAND="ssh -v" git push origin <branch>` is fine.
    
    If it returns *anything* (custom IdentityFile, IdentityAgent, deploy-key flags, etc.), DO NOT use `GIT_SSH_COMMAND="ssh -v"`. It REPLACES `core.sshCommand` entirely, dropping every flag. Output will look like the wrong keys are being offered, because they are, but only because you removed the constraint.
    
    Append `-v` to the existing command instead:
    
    ```
    GIT_SSH_COMMAND="$(git config core.sshCommand) -v" git push origin <branch>
    ```
    
    ## Background push gotcha
    
    If you started a push with `run_in_background` and then ran a foreground retry (e.g., because the first looked stuck), the background push may have already succeeded. Before re-investigating "why is push failing":
    
    1. `git -C <worktree> log --oneline origin/<branch>..HEAD`. Empty output means the push went through.
    2. Verify retry's cwd: `pwd` and `git rev-parse --show-toplevel`.
    3. `gh pr view <pr>` to see if the commit landed.
    
    Don't escalate to "SSH might be broken" before confirming the push didn't already complete.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.