mcpField
P
push-skill-to-github

push-skill-to-github

github.com/davidondrejAgent workflows4.2k182 installsUpdated today
Repository

About push-skill-to-github

An agent skill for committing skill changes in the canonical `~/.agents` repository and pushing them to GitHub. It describes how to avoid unrelated changes and verify that the push succeeded.

Key features

  1. 01Check pending repository changes
  2. 02Stage and commit skill updates
  3. 03Push changes from the repository root
  4. 04Verify the push result

Use cases

  1. 01Publish an edited skill after user approval
  2. 02Commit only the changed skill folders
  3. 03Confirm a push reached `main`

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/davidondrej/skills --skill push-skill-to-github

After installing, type/push-skill-to-githubin Claude Code to confirm it loaded.

Details

From the project README

Push Skills to GitHub

For committing any skill change to the user's private skills repo: <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

Run git directly in the current shell. A push is a quick synchronous command — no persistent terminal, pane, or cmux needed.

  1. 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.
  2. Stage, commit, push: 
    cd ~/.agents && git add skills/<skill-name> && git commit -m "<concise message>" && git push
  3. 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.

Comments

Markdown supported