| name | push-skill-to-github |
| description | 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, and pushing directly in the current shell — works in any agent, no cmux needed. |
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 — 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
Run git directly in the current shell. A push is a quick synchronous command — no persistent terminal, pane, or cmux needed.
- Check what's pending in
~/.agents:
cd ~/.agents && git status --short
If there are unrelated uncommitted changes, stage only the skill folder(s) you changed — don't bundle unrelated work under one commit message.
- Stage, commit, push:
cd ~/.agents && git add skills/<skill-name> && git commit -m "<concise message>" && git push
- Verify the push landed: the push output must show
main -> main. If it doesn't, report the error — don't claim success.
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.
