agentsclimarketplace
Sign in

Github ship

Skill arclabshq/arc-labs-studio-team/skills/github-ship

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.From its SKILL.md

Install
npx -y skills add arclabshq/arc-labs-studio-team --skill github-ship

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 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.

SKILL.md

1.8 KB, 310 tokens by cl100k_base, 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

  1. Confirm the repository, remote, branch, visibility, and requested end state.
  2. Inspect repository status before editing or staging. Stop for unrelated or unclear changes that could be swept into the shipment.
  3. Review the full diff and identify generated, secret, personal, or accidental files.
  4. Run the repository's relevant checks and inspect user-visible output when applicable.
  5. Stage only the intended files and review the staged diff.
  6. Write a concise commit message that describes the outcome.
  7. Push the task branch and create or update the pull request with purpose, examples, validation, and known limitations.
  8. 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.

What ships with it: 1 file

258 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.