agentleFS
haruharu/redmine_ai_helper/.claude/skills/speckit-branch-convention-rename/SKILL.md

speckit-branch-convention-rename

Skill107 starsChanged 9 months agoMITView on GitHub

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

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Verify a spec-kit project exists by checking for .specify/ directory

    line 29
  2. Very specific:

    If no convention is configured, inform the user and suggest running /speckit.branch-convention.configure first

    line 31
  3. Distinctive:

    Verify the working tree is clean (no uncommitted changes) — renaming with dirty state risks data loss

    line 32
  4. Distinctive:

    Confirm with user: Ask for explicit confirmation before proceeding.

    line 59
  5. Distinctive:

    Update internal references: Search spec.md, plan.md, tasks.md for references to the old folder/branch name and update them

    line 63
  6. Distinctive:

    Update tracking: If branch tracks a remote, inform user to update remote separately

    line 65
  7. Distinctive:

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

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

$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:

    # 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

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.