Shell Tool · engineering · Sentinel

Push to GitHub

Initialize /work as a git repo, create the GitHub repo, push, return the URL.

Updated today

View as MarkdownsentinelsonnetcheapMax 5 turns

Overview

Wraps ultron-github-push: inits /work as a git repo if needed, commits the current state, creates the GitHub repo under the user's account using GH_TOKEN, pushes the initial commit, returns the repo URL. Optionally opens a draft PR if --pr is requested.

When to use this

user wants to push /work to a new GitHub repo
user says 'put this on GitHub' / 'create a repo for this' / 'open-source this'
user wants the code shareable / under version control externally

When NOT to use this

user already has a remote and just wants to commit + push → use shell_exec with git directly
user wants to fork an existing repo → use shell_exec with gh CLI directly

Example prompts

push this to GitHub as a new repo named cool-app

create a GitHub repo for this and push it

open-source this with the name foo-bar

Inputs and output

Inputs

Field	Description
`repo_name`	kebab-case GitHub repo name
`private`	true\|false (default false)

Output

GitHub repo URL.

Runtime profile

What the engine commits when this skill runs.

Property	Value	Meaning
Model tier	`sonnet`	The balanced default model class. Trades quality against cost for the vast majority of skill runs.
Cost class	`cheap`	A small, fast model. Cents per invocation.
Turn budget	`5`	Hard cap on tool-calling iterations before the engine forces a final answer.
Execution	`synchronous`	Runs inside the live turn; result lands in the same response.

Under the hood

Tools the engine exposes to this skill and integrations it needs.

Resource	Kind
`shell_exec`	tool
`github`	integration

Tags: engineering, github, ship

Execution template

Shell tools dispatch via a command template. The model substitutes user inputs into the placeholders before firing the underlying tool.

shell_execbash

1ultron-github-push {{repo_name}}

Related skills

Skill	What it does
Spin up a Web App	Scaffold a fresh web app in /work, start the dev server, surface the live preview URL.
Clone a Website	Fire ultron-capture: spider the site, deploy a branded clone, surface the URL when ready.
Build an Agent	Spin up an autonomous agent on the agent-runtime satellite — try templates first, custom build only if no fit.
Deploy to Cloudflare	Ship the current /work to Pages, Workers, or Containers — then verify the live URL.
Swap Page Sections	Reorder <section> blocks in a minified HTML file with byte-level safety.
Refactor Across Files	Multi-file string operations with quote and escape safety — uses bun -e, not sed.

Invoking this from an agent

Three paths reach this skill. From the chat UI, a user can type the persona slash command followed by a natural request and the discovery step resolves to this skill automatically. From the MCP server, fetch the skill detail with get_skill({id: "push-to-github"}) and then invoke it through the agent runtime once the authenticated tier ships. From your own code, hit /docs/skills/push-to-github/llm.txt for the token-efficient markdown body and feed it to your model directly.

Note

Every skill page has a canonical permalink and a markdown alternate that LLM crawlers consume via Accept: text/markdown. The full machine-readable catalog lives at /.well-known/agent-skills/index.json.