agentsclimarketplace

Git branch rename

Skill JasonWarrenUK/goblin-mode/skills/git-branch-rename

Three goblins in a trenchcoat pretending to be a senior developer. Claude Code config shaped by ADHD, friction, and spite.

Install
npx -y skills add JasonWarrenUK/goblin-mode --skill git-branch-rename

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.

What its author says it does

Copied from the file, not written here

{{ ƔƔƔ }} Check the current branch name against convention (type/short-description) and rename it if it drifted — e.g. work started on a misnamed or default branch.

SKILL.md

1.5 KB, as published. Nobody here has run it

Assess and Rename Current Branch

  1. If user has specified a new name, apply it; otherwise, get the current branch name with git branch --show-current
  2. Get a summary of what's actually been done on this branch:
    • git log main..HEAD --oneline to see commits
    • git diff main..HEAD --name-only to see changed files
  3. Compare the branch name against the actual changes:
    • Does the name still accurately describe the work?
    • Is the scope broader or narrower than the name implies?
    • Does the name follow the <prefix>/<short-description> convention?
  4. If the name is still accurate, say so and stop
  5. If a rename is warranted, suggest a better name and explain why
    • Format: <prefix>/<short-description> — all lowercase, hyphens, imperative mood (add-feature not adds-feature or adding-feature)
  6. Await approval — if accepted:
    • Rename locally: git branch -m <new-name>
    • Rename on remote: git push origin HEAD:<new-name> then git push origin --delete <old-name>
    • Set upstream: git branch --set-upstream-to=origin/<new-name>

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.