New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Speckit Branch Convention Rename

by haru in haru/redmine_ai_helper

Rename non-compliant branches and spec folders to match the configured convention

MITAuto-check passedDevelopment

Install Speckit Branch Convention Rename

skills CLI
$ npx skills add haru/redmine_ai_helper --skill speckit-branch-convention-rename -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install haru/redmine_ai_helper speckit-branch-convention-rename --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/haru/redmine_ai_helper.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/speckit-branch-convention-rename .claude/skills/speckit-branch-convention-rename && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
speckit-branch-convention-rename
GitHub stars
106
Token cost
~1k tokens
SKILL.md length
426 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Rename non-compliant branches and spec folders to match the configured convention

  • Works in 4 steps: Verify a spec-kit project exists by… → Load convention config from… → If no convention is configured, inform… → …
  • Tasks that involve Spec-driven development
  • SKILL.md covers User Input, Prerequisites, Outline and Rules
  • Calls git

What it does

Speckit Branch Convention Rename is an agent skill from haru/redmine_ai_helper. Rename non-compliant branches and spec folders to match the configured convention

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires spec-kit project structure with .specify/ directory

It sits in Development, covering Spec-driven development. The repository describes itself as: A Redmine plugin that adds AI agents, MCP Server, smart completion, and vector search. The licence is MIT.

When your agent uses it

  • Tasks that involve Spec-driven development

Example prompts

  • “/speckit-branch-convention-rename”

Requirements

  • Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Verify a spec-kit project exists by checking for .specify/ directory
  2. Load convention config from .specify/branch-convention.yml
  3. If no convention is configured, inform the user and suggest running /speckit.branch-convention.configure first
  4. Verify the working tree is clean (no uncommitted changes) — renaming with dirty state risks data loss

What it can do on your machine

Read from SKILL.md and the folder at commit 3cd87d6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires spec-kit project structure with .specify/ directory

    From compatibility in the SKILL.md frontmatter.

Context cost

Speckit Branch Convention Rename loads about 1k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 426 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from haru/redmine_ai_helper at commit 3cd87d6, republished under its MIT licence (© haru). 426 words, ~1,029 tokens.

Download SKILL.mdSave it as .claude/skills/speckit-branch-convention-rename/SKILL.md (or your agent's skills folder).
name
speckit-branch-convention-rename
description
Rename non-compliant branches and spec folders to match the configured convention
compatibility
Requires spec-kit project structure with .specify/ directory
metadata.author
Quratulain-bilal
metadata.source
extension:branch-convention
user-invocable
true
disable-model-invocation
false

Branch Convention Rename Skill

Rename to Convention

Rename non-compliant Git branches and spec folders to match the configured naming convention. Handles both branch renaming and folder moving with full safety checks.

User Input

text
$ARGUMENTS

You MUST consider the user input before proceeding (if not empty). The user may specify a specific branch to rename (e.g., "004-chat-system") or "all" to rename everything non-compliant.

Prerequisites

  1. Verify a spec-kit project exists by checking for .specify/ directory
  2. Load convention config from .specify/branch-convention.yml
  3. If no convention is configured, inform the user and suggest running /speckit.branch-convention.configure first
  4. Verify the working tree is clean (no uncommitted changes) — renaming with dirty state risks data loss

Outline

  1. Run validation first: Execute the same checks as /speckit.branch-convention.validate to identify all non-compliant branches and folders.

  2. Build rename plan: For each non-compliant item, compute the correct name:

    Current NameConventionNew NameAction
    004-chat-system{type}/{seq}-{kebab}feat/004-chat-systemRename branch, keep folder
    5-api{seq}-{kebab} (pad 3)005-apiRename branch + move folder
    PROJ142-auth{ticket}-{kebab}PROJ-142-authRename branch + move folder

  3. Present the rename plan: Show a preview table before making any changes:

    markdown
    # Rename Plan

| # | Current Branch | New Branch | Current Folder | New Folder |
|---|---------------|------------|----------------|------------|
| 1 | 004-chat-system | feat/004-chat-system | 004-chat-system | 004-chat-system (unchanged) |
| 2 | 5-api | feat/005-api | 5-api | 005-api |

**Actions**: {N} branches to rename, {M} folders to move

  4. Confirm with user: Ask for explicit confirmation before proceeding. This is a destructive operation.

  5. Execute renames (after confirmation): For each item in the plan:

    • Rename spec folder: git mv specs/{old} specs/{new} (preserves git history)
    • Update internal references: Search spec.md, plan.md, tasks.md for references to the old folder/branch name and update them
    • Rename git branch: git branch -m {old} {new}
    • Update tracking: If branch tracks a remote, inform user to update remote separately

  6. Update references in artifacts: After renaming, scan all spec artifacts for stale references:

    • spec.md header metadata (branch name field)
    • plan.md header metadata
    • tasks.md header metadata
    • Any cross-references between features

  7. Report: Output a summary:

    • How many branches were renamed
    • How many folders were moved
    • How many artifact references were updated
    • Any items that could not be renamed (e.g., currently checked-out branch conflicts)
    • Suggest next step: /speckit.branch-convention.validate to confirm all items are now compliant
Show full SKILL.md (96 more words)Show less

Rules

  • Never rename without confirmation — always show the plan first and wait for explicit approval
  • Clean working tree required — refuse to rename if there are uncommitted changes
  • Use git mv for folders — preserves git history and tracking
  • Update all references — scan artifacts for old names and update to new names
  • Never rename main/master/develop — only rename spec-kit feature branches
  • Handle checked-out branch — if the current branch needs renaming, rename it last using git branch -m
  • Remote branches are informational only — report that remote branches need manual update (git push origin :{old} {new}) but do not push automatically

© haru, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/speckit-branch-convention-rename of haru/redmine_ai_helper.

Open the folder on GitHubat commit 3cd87d6

Compare with similar skills

Speckit Branch Convention Rename next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Speckit Branch Convention Rename compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Speckit Branch Convention Rename this skillharu/redmine_ai_helper106—~1kAutomated safety check: PassMIT
OpenSpec Bulk Change ArchiverFission-AI/OpenSpec72k2 repos~5.6kAutomated safety check: PassMIT
Speckit ConstitutionWeihanLi/WeihanLi.Common24212 repos~2.1kAutomated safety check: PassApache-2.0
Speckit Plankunstmusik/blue15419 repos~2.1kAutomated safety check: PassGPL-3.0
Speckit Specifykunstmusik/blue15419 repos~4.7kAutomated safety check: PassGPL-3.0
Review Spdzhu1090093659/spec_driven_develop987—~1.5kAutomated safety check: PassMIT

Similar skills

  • OpenSpec Bulk Change Archiver

    Fission-AI/OpenSpec

    Archives several completed OpenSpec changes in one operation, checking the codebase to resolve spec conflicts rather than archiving blindly.

    72k GitHub starsUsed in 2 repos~5.6k tokens
    DevelopmentAuto-check passed

  • Speckit Constitution

    WeihanLi/WeihanLi.Common

    Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

    242 GitHub starsUsed in 12 repos~2.1k tokens
    DevelopmentAuto-check passed

  • Speckit Plan

    kunstmusik/blue

    Execute the implementation planning workflow using the plan template to generate design artifacts.

    154 GitHub starsUsed in 19 repos~2.1k tokens
    DevelopmentAuto-check passed

  • Speckit Specify

    kunstmusik/blue

    Create or update the feature specification from a natural language feature description.

    154 GitHub starsUsed in 19 repos~4.7k tokens
    DevelopmentAuto-check passed

  • Review Spd

    zhu1090093659/spec_driven_develop

    Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop.

    987 GitHub stars~1.5k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Speckit Tasks

    kunstmusik/blue

    Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

    154 GitHub starsUsed in 19 repos~3k tokens
    DevelopmentAuto-check passed

More from haru/redmine_ai_helper

All 23 skills in this repo

  • Commit

    haru/redmine_ai_helper

    Stage the current changes and create a git commit with a properly formatted English message.

    106 GitHub stars~1.1k tokensUpdated today
    Auto-check: notes

  • Create Pull Request

    haru/redmine_ai_helper

    Create a pull request from the current branch. An agent skill from haru/redmine_ai_helper.

    106 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Create Release Branch

    haru/redmine_ai_helper

    Create a release branch for a given version. An agent skill from haru/redmine_ai_helper.

    106 GitHub stars~599 tokensUpdated today
    Auto-check passed

  • Record Code Review Feedback

    haru/redmine_ai_helper

    Record code review findings (GitHub Copilot PR review or a local AI review) that led to a code change in docs/code-review-feedback/ as append-only entries with root-cause analysis.

    106 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Record Spec Feedback

    haru/redmine_ai_helper

    Record a user's correction of an AI-written specification in docs/spec-feedback/ as an append-only entry with root-cause analysis.

    106 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Qlty Check

    haru/redmine_ai_helper

    Code quality checks, formatting, and metrics via qlty CLI. An agent skill from haru/redmine_ai_helper.

    106 GitHub starsUsed in 2 repos~628 tokens
    Auto-check passed

Categories

Questions about Speckit Branch Convention Rename

What does Speckit Branch Convention Rename do?

Rename non-compliant branches and spec folders to match the configured convention. Speckit Branch Convention Rename is an agent skill from haru/redmine_ai_helper.

When should I use Speckit Branch Convention Rename?

Speckit Branch Convention Rename fits situations like: tasks that involve Spec-driven development.

How do I install Speckit Branch Convention Rename in Claude Code?

Run `npx skills add haru/redmine_ai_helper --skill speckit-branch-convention-rename -a claude-code`. Or copy the skill folder (.claude/skills/speckit-branch-convention-rename in haru/redmine_ai_helper) into .claude/skills/speckit-branch-convention-rename in your project. Claude Code loads it when a task matches its description.

How do I install Speckit Branch Convention Rename in Codex?

Run `npx skills add haru/redmine_ai_helper --skill speckit-branch-convention-rename -a codex`. Or copy the skill folder (.claude/skills/speckit-branch-convention-rename in haru/redmine_ai_helper) into .agents/skills/speckit-branch-convention-rename in your project. Codex loads it when a task matches its description.

Can I use Speckit Branch Convention Rename in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add haru/redmine_ai_helper --skill speckit-branch-convention-rename -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/speckit-branch-convention-rename, .gemini/skills/speckit-branch-convention-rename, .github/skills/speckit-branch-convention-rename and .opencode/skills/speckit-branch-convention-rename in your project.

What does Speckit Branch Convention Rename need to run?

Going by SKILL.md and its folder, Speckit Branch Convention Rename needs the command-line tools its instructions call (git). Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory.

Does Speckit Branch Convention Rename access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Speckit Branch Convention Rename safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Speckit Branch Convention Rename use?

Speckit Branch Convention Rename is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Speckit Branch Convention Rename use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Speckit Branch Convention Rename?

Skills that share tags, products or a category with Speckit Branch Convention Rename: OpenSpec Bulk Change Archiver (Fission-AI/OpenSpec, 72k stars), Speckit Constitution (WeihanLi/WeihanLi.Common, 242 stars), Speckit Plan (kunstmusik/blue, 154 stars) and Speckit Specify (kunstmusik/blue, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Speckit Branch Convention Rename?

haru (a GitHub user) maintains it in haru/redmine_ai_helper, which has 106 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 10, 2026.

Source: haru/redmine_ai_helper on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.