Install
$ agentstack add skill-technicalpickles-pickled-claude-plugins-push ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
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:
lefthookorhook: pre-push→ pre-push hook failed; transport was finePermission 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 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
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":
git -C log --oneline origin/..HEAD. Empty output means the push went through.- Verify retry's cwd:
pwdandgit rev-parse --show-toplevel. gh pr viewto see if the commit landed.
Don't escalate to "SSH might be broken" before confirming the push didn't already complete.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: technicalpickles
- Source: technicalpickles/pickled-claude-plugins
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.