agentsclimarketplace
Sign in

New branch

Skill BjornMelin/dev-skills/skills/new-branch

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

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

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.

What ships with it: 1 file

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