agentsclimarketplace

Ship branch

Skill BjornMelin/dev-skills/skills/ship-branch

AgentSkills library: reusable skills for AI coding agents (AI SDK, Codex, LangGraph, Supabase, Docker, Vitest, pytest, Streamlit, Zod).

Install
npx -y skills add BjornMelin/dev-skills --skill ship-branch

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 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

Finalize a branch by staging only task-related files, splitting work into semantic reviewable conventional commits, pushing to remote, and opening a PR into main with a conventional-commits title and reviewer-ready body. Use when the user asks to commit, push, and open a PR, or to scaffold missing repo PR/release defaults on request.

SKILL.md

1.5 KB, 274 tokens by cl100k_base, as published. Nobody here has run it

Ship Branch

Workflow

  1. Inspect git status --short first.
  2. Leave unrelated dirty files untouched.
  3. Group changes by semantic purpose and split mixed work into separate commits when needed.
  4. Use short scoped Conventional Commit messages that match the change.
  5. If the current branch is main, create a working branch first; otherwise stay on the current branch.
  6. Commit all intended changes before pushing.
  7. Push the branch to the remote.
  8. Open a PR into main with gh pr create.
  9. Use a Conventional Commits PR title and a reviewer-ready PR body built from repo-defaults.md.

Commit Rules

  • Prefer one commit per semantic change.
  • Keep commit order aligned to reviewer value: feat, fix, test, docs, refactor, chore.
  • Do not stage unrelated files or use git add . unless the whole task is one coherent change.
  • Stop if the tree is too mixed to separate cleanly or ownership is ambiguous.

Repo Defaults On Request

  • If the user explicitly asks to create missing repo defaults, scaffold the files from repo-defaults.md.
  • Otherwise, do not add repo-level template or Release Please files.

Keep looking

Skills are one crate of 328,083. 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.