How do I install the Push Skill To Github skill?

Run npx skillmds add solizardking/push-skill-to-github 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 Push Skill To Github 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 Push Skill To Github?

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 Push Skill To Github free to use?

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

Who published Push Skill To Github?

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

Push Skill To Github by solizardking

Name: Push Skill To Github
Rating: 4.2 (5 reviews)
Author: Solizardking

Push Skill To Github

Commit and push agent-skill changes to the user's private skills GitHub repo (rooted at ~/.agents). Use after creating or updating any skill, when the user says "push the skill", "push skills to github", "save the skill to my repo", or "update the skills repo". Handles staging, committing, pushing, and cleaning up the cmux pane used to do it.

Solizardking d53dcfa 2.2 KB Updated Sep 9, 2026 0 repo stars

File contents

Push Skills to GitHub

For committing any skill change to the user's private skills repo, git root ~/.agents (this is also the canonical skill folder; .claude and .pi/agent/skills symlink to ~/.agents/skills). Pushes here auto-publish a sanitized public mirror to davidondrej/skills — never push directly to that public repo.

Use this after creating or editing a skill. If the skill is distributed to all agents, do that first (distribute-skill-to-all-agents), then run this to push the canonical copy.

Steps

Not in cmux? (no $CMUX_WORKSPACE_ID): skip the cmux pane steps — just run the git commands from step 2 directly in any available terminal, then verify the push output.

Open a fresh cmux pane in the current workspace, no focus steal:

cmux new-pane --type terminal --direction right --workspace "$CMUX_WORKSPACE_ID" --focus false
cmux list-panes --workspace "$CMUX_WORKSPACE_ID"   # note the NEW pane + its surface ref

Stage, commit, push in ~/.agents (send to the new pane's surface):

cmux send --surface surface:NEW 'cd ~/.agents && git add -A && git commit -m "<concise message>" && git push'
cmux send-key --surface surface:NEW enter

Verify the push landed:

sleep 2
cmux read-screen --surface surface:NEW | tail -15   # expect "main -> main"

Close the pane once confirmed:

cmux close-surface --surface surface:NEW
cmux list-panes --workspace "$CMUX_WORKSPACE_ID"    # confirm the pane is gone

Notes

Always run git from ~/.agents (the repo root), not ~/.agents/skills.
Write a concise, specific commit message describing the skill change.
Only push to GitHub when the user asks. Don't push speculatively.

---name: push-skill-to-githubdescription: Commit and push agent-skill changes to the user's private skills GitHub repo (rooted at ~/.agents). Use after creating or updating any skill, when the user says "push the skill", "push skills to github", "save the skill to my repo", or "update the skills repo". Handles staging, committing, pushing, and cleaning up the cmux pane used to do it.--- # Push Skills to GitHub For committing any skill change to the user's private skills repo, git root **`~/.agents`** (this is also the canonical skill folder; `.claude` and `.pi/agent/skills` symlink to `~/.agents/skills`). Pushes here auto-publish a sanitized public mirror to `davidondrej/skills` — never push directly to that public repo. Use this after creating or editing a skill. If the skill is distributed to all agents, do that first (`distribute-skill-to-all-agents`), then run this to push the canonical copy. ## Steps **Not in cmux?** (no `$CMUX_WORKSPACE_ID`): skip the cmux pane steps — just run the git commands from step 2 directly in any available terminal, then verify the push output. 1. **Open a fresh cmux pane** in the current workspace, no focus steal: ```bash cmux new-pane --type terminal --direction right --workspace "$CMUX_WORKSPACE_ID" --focus false cmux list-panes --workspace "$CMUX_WORKSPACE_ID" # note the NEW pane + its surface ref ``` 2. **Stage, commit, push** in `~/.agents` (send to the new pane's surface): ```bash cmux send --surface surface:NEW 'cd ~/.agents && git add -A && git commit -m "<concise message>" && git push' cmux send-key --surface surface:NEW enter ``` 3. **Verify** the push landed: ```bash sleep 2 cmux read-screen --surface surface:NEW | tail -15 # expect "main -> main" ``` 4. **Close the pane** once confirmed: ```bash cmux close-surface --surface surface:NEW cmux list-panes --workspace "$CMUX_WORKSPACE_ID" # confirm the pane is gone ``` ## Notes - Always run git from `~/.agents` (the repo root), not `~/.agents/skills`. - Write a concise, specific commit message describing the skill change. - Only push to GitHub when the user asks. Don't push speculatively.

Frequently asked questions