gp
Skill1 starsChanged 4 months agoMITView on GitHub
Git push with checks and report. Used when the user writes "push", "gp", "git push".
- Commits and pushes
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- sync-docsSkill
- yoke-createSkill
- yoke-releaseSkill
- yoke-validateSkill
- bootstrapSkill
- doSkill
- draftSkill
- gcaSkill
- grill-docsSkill
- grillSkill
- handoffSkill
- helpSkill
- issuesSkill
- journalSkill
- mergeSkill
- prdSkill
- prSkill
- reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 59
If PUSH_STATUS = FAILED → show PUSH_ERROR.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Git push with checks and report
Push orchestrator: collect state, push, report. Runs autonomously — no confirmation prompts.
Input
$ARGUMENTS — optional flags (--force-with-lease).
Step 1 — Pre-check
One call:
bash ${CLAUDE_PLUGIN_ROOT}/lib/gp-precheck.shParse the structured block. Single-value fields are KEY: value; list fields (UNCOMMITTED_LIST) span from the line after KEY: to the next top-level KEY:.
Step 2 — Decide
Blocking (report and stop):
ERRORScontainsdetached HEAD→ "Checkout a branch before push".ERRORScontainsno remote→ "Add a remote:git remote add origin <url>".UNPUSHED_COMMITS = 0andHAS_UPSTREAM = true→ "Nothing to push" (ifUNCOMMITTED_FILES > 0, add: commit first with/yoke:gca).
Non-blocking:
GH_AUTH != ok→ push still proceeds; only PR/URL info is skipped in the report.UNCOMMITTED_FILES > 0→ never blocks.git pushsends only commits; note them in the report.
PUSH_MODE:
HAS_UPSTREAM = false→set-upstream$ARGUMENTScontains--force-with-lease→force-with-lease- otherwise →
normal
Step 3 — Push
One call:
bash ${CLAUDE_PLUGIN_ROOT}/lib/gp-push.sh "<BRANCH>" "<PUSH_MODE>"If PUSH_STATUS = FAILED → show PUSH_ERROR. If it contains "non-fast-forward" → suggest git pull --rebase or /yoke:gp --force-with-lease. Stop.
Step 4 — Report
Fill from the gp-push.sh block; Commits: ← PUSHED_LIST:
Pushed to origin/<BRANCH>: +<PUSHED_COMMITS> commits
Commits:
<PUSHED_LIST>
Stats: <DIFF_STAT>
Link: <BRANCH_URL>- Omit the
Link:line whenBRANCH_URL = empty. PR_EXISTS = true→ addPR: <PR_TITLE> (<PR_URL>)and suggest/yoke:prto update it.PR_EXISTS = false→ suggest/yoke:prto create one.UNCOMMITTED_FILES(carried from Step 1)> 0→ addUncommitted (not pushed): <N> files.
Print the report and the suggestion — do not ask a follow-up question.
Rules
- Runs autonomously: no confirmation prompts.
- Remote:
origin. When multiple remotes exist — push to origin. ghis optional; its absence only removes PR/URL info, never blocks the push.- The only mutation is
git push(insidelib/gp-push.sh). - Output limit: max 20 commits.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

