How do I install the Github Push Via Fox skill?

Run npx skillmds@latest add rewse/github-push-via-fox in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Push Via Fox safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Push Via Fox?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Push Via Fox free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Push Via Fox?

rewse (@rewse) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Push Via Fox by rewse — Agent Skill

Name: Github Push Via Fox
Rating: 4.2 (5 reviews)
Author: rewse

Github Push Via Fox

Push commits to GitHub from this host by relaying them through fox. Use this skill whenever a push to github.com fails or hangs, when git reports GH007 or rejects the author email, or before pushing any repository whose origin is on GitHub from this host. Covers both uncommitted working-tree changes and commits already made locally. Does not apply to other remotes such as internal GitLab, which push directly.

rewse Updated Sep 22, 2026

File contents

Push to GitHub via fox

This host cannot reach github.com for pushes. Relay the work to fox and push from there. Other remotes are unaffected and push directly from here.

Pick the transfer method by whether the work is committed yet.

Uncommitted working-tree changes

The result collapses into a single commit on fox.

Generate a patch here: git -P diff -- <files> > /tmp/changes.patch
Copy it over: scp /tmp/changes.patch fox:/tmp/changes.patch
On fox, update the repo and apply: cd <repo path on fox> && git pull --ff-only && git apply --check /tmp/changes.patch && git apply /tmp/changes.patch
Commit and push: git commit -m "..." && git push origin HEAD

Local commits already made

Commit history is preserved.

Export the unpushed commits: git format-patch origin/main..HEAD -o /tmp
Copy them over: scp /tmp/000*.patch fox:/tmp/
On fox, update the repo and apply in order: cd <repo path on fox> && git pull --ff-only && git am /tmp/000*.patch
Push: git push origin HEAD

After pushing

Sync this host with git pull, or chezmoi update for the chezmoi repo.

If the local commits and the pushed commits differ, run git reset --hard origin/main to adopt the remote versions. Do not ask for confirmation on this step; it is pre-approved. Confirm the trees match first with git diff HEAD origin/main, where empty output means the working tree is identical and nothing is lost.

Author rejected

If GitHub rejects the push with GH007, do not hand-write --author. The noreply address is not taking effect: check that git config --show-origin --get user.email resolves to github.inc, and that no ~/.gitconfig is overriding it.

---name: github-push-via-foxdescription: Push commits to GitHub from this host by relaying them through fox. Use this skill whenever a push to github.com fails or hangs, when git reports GH007 or rejects the author email, or before pushing any repository whose origin is on GitHub from this host. Covers both uncommitted working-tree changes and commits already made locally. Does not apply to other remotes such as internal GitLab, which push directly.---# Push to GitHub via foxThis host cannot reach `github.com` for pushes. Relay the work to `fox` and push from there. Other remotes are unaffected and push directly from here.Pick the transfer method by whether the work is committed yet.## Uncommitted working-tree changesThe result collapses into a single commit on `fox`.1. Generate a patch here: `git -P diff -- <files> > /tmp/changes.patch`2. Copy it over: `scp /tmp/changes.patch fox:/tmp/changes.patch`3. On `fox`, update the repo and apply: `cd <repo path on fox> && git pull --ff-only && git apply --check /tmp/changes.patch && git apply /tmp/changes.patch`4. Commit and push: `git commit -m "..." && git push origin HEAD`## Local commits already madeCommit history is preserved.1. Export the unpushed commits: `git format-patch origin/main..HEAD -o /tmp`2. Copy them over: `scp /tmp/000*.patch fox:/tmp/`3. On `fox`, update the repo and apply in order: `cd <repo path on fox> && git pull --ff-only && git am /tmp/000*.patch`4. Push: `git push origin HEAD`## After pushingSync this host with `git pull`, or `chezmoi update` for the chezmoi repo.If the local commits and the pushed commits differ, run `git reset --hard origin/main` to adopt the remote versions. Do not ask for confirmation on this step; it is pre-approved. Confirm the trees match first with `git diff HEAD origin/main`, where empty output means the working tree is identical and nothing is lost.## Author rejectedIf GitHub rejects the push with GH007, do not hand-write `--author`. The noreply address is not taking effect: check that `git config --show-origin --get user.email` resolves to `github.inc`, and that no `~/.gitconfig` is overriding it.

Frequently asked questions