agentsclimarketplace

New branch

Skill BjornMelin/dev-skills/skills/new-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 new-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

Create and switch to a new conventional-commit and semver-compliant branch before doing any work, then present the full execution plan for that branch and its pull request. Use when the user wants a branch prepared first and a clear plan in chat before implementation.

SKILL.md

0.8 KB, 122 tokens by cl100k_base, as published. Nobody here has run it

New Branch

  1. Before any other work, inspect the current branch/worktree state.
  2. Create and checkout a new branch for the task using a conventional-commit and semver-compliant name, keeping it short and scoped, for example feat/add-x, fix/y, or chore/z.
  3. Stop after switching to the new branch unless the user separately asks for implementation work.
  4. In chat, provide the complete plan for work to be done on that branch and its pull request: intended changes, key files, verification, commit shape, and any risks or blockers.

Gives 0 of the 12 instructions most pr commit review skills give in 122 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

  • use conventional commits formatin 123 of 888, across 110 files
  • keep subject line under 72 charactersin 60 of 888, across 46 files
  • delete branches after mergein 50 of 888, across 37 files
  • use imperative mood in subject linein 50 of 888, across 41 files
  • use imperative mood in commit messagesin 45 of 888
  • generate a conventional commit messagein 42 of 888
  • make atomic commitsin 37 of 888, across 25 files
  • run tests before committingin 36 of 888, across 24 files
  • run project test suite to verify clean baselinein 35 of 888, across 7 files
  • run detected project setup commandsin 34 of 888, across 6 files
  • wrap commit body at 72 charactersin 32 of 888, across 25 files
  • split unrelated changes into separate commitsin 32 of 888, across 27 files

Said here and by no other author read

  • use a conventional-commit and semver-compliant branch name
  • keep the branch name short and scoped
  • provide the complete plan in chat
  • include intended changes in the plan
  • list key files in the plan
  • describe verification steps in the plan

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

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.