Github ship
A portable studio team of reusable AI roles and workflows for Claude, Codex, Gemini, and Grok.
npx -y skills add arclabshq/arc-labs-studio-team --skill github-shipAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Reviews a scoped change, validates it, commits intentionally, pushes a branch, and opens or updates a clear GitHub pull request. Use when the user explicitly asks to ship, publish, push, commit, or prepare repository work for review.
SKILL.md
1.8 KB, as published. Nobody here has run it
GitHub Ship
Publish only the intended, verified change. Treat repository visibility, branch, remote, and included files as part of the safety boundary.
Shipping sequence
- Confirm the repository, remote, branch, visibility, and requested end state.
- Inspect repository status before editing or staging. Stop for unrelated or unclear changes that could be swept into the shipment.
- Review the full diff and identify generated, secret, personal, or accidental files.
- Run the repository's relevant checks and inspect user-visible output when applicable.
- Stage only the intended files and review the staged diff.
- Write a concise commit message that describes the outcome.
- Push the task branch and create or update the pull request with purpose, examples, validation, and known limitations.
- Read back the remote state and report the branch, commit, checks, and review URL.
New public repositories
Before creating a repository, scan the entire proposed history and working tree for private paths, credentials, personal data, internal documents, and license gaps. Confirm the exact owner, name, and public visibility. Never make an existing private repository public as a shortcut when a clean export is safer.
Boundaries
Do not stage unrelated changes, bypass failed checks, force-push, merge, delete branches, change visibility, or create a public repository unless the user has authorized that outcome. Never place secrets in a commit or pull request, even temporarily.