armelhbobdad/oh-my-skills / .claude/skills/skf-rename-skill
skf-rename-skill
VerifiedRename a skill across all its versions — transactional copy-verify-delete with platform context rebuild. Use when the user requests to "rename a skill."
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.6 KB |
| customize.toml | config | 3.0 KB |
| references/execute.md | markdown | 32.7 KB |
| references/exit-codes.md | markdown | 3.6 KB |
| references/health-check.md | markdown | 897 B |
| references/invocation-contract.md | markdown | 4.9 KB |
| references/report.md | markdown | 9.2 KB |
| references/select.md | markdown | 31.8 KB |
| scripts/skf-validate-rename-name.py | script | 12.8 KB |
customize.toml
View on GitHub# DO NOT EDIT -- overwritten on every update.
#
# Workflow customization surface for skf-rename-skill.
# Team overrides: {project-root}/_bmad/custom/skf-rename-skill.toml
# Personal overrides: {project-root}/_bmad/custom/skf-rename-skill.user.toml
[workflow]
# --- Configurable below. Overrides merge per BMad structural rules: ---
# scalars: override wins • arrays (persistent_facts, activation_steps_*): append
# arrays-of-tables with `code`/`id`: replace matching items, append new ones.
# Steps to run in On Activation step 3, after config load and headless
# resolution and before the workflow's first step (select.md). Overrides
# append. Use for org-wide pre-flight checks (audit-log emit,
# ticket-reference enforcement) that must precede any rename work.
activation_steps_prepend = []
# Steps to run at the end of On Activation, after the prepend steps and
# the persistent facts load, just before select.md loads. Overrides append.
# Use for context loads or banner customization.
activation_steps_append = []
# Persistent facts the workflow keeps in mind for the whole run
# (rename-policy reminders, public-name-stability rules, audit guardrails).
# Overrides append.
#
# Each entry is one of:
# - a literal sentence, e.g. "Renames of skills tagged `published` require approval."
# - a file reference prefixed with `file:`, e.g.
# "file:{project-root}/docs/rename-policy.md" (globs supported; file
# contents are loaded and treated as facts).
# - an entry prefixed with `!`, which loads nothing and drops each earlier
# entry it names.
#
# The default below loads every project-context.md under {project-root}.
# Overrides append, so they cannot delete it; to stop loading those files,
# set in {project-root}/_bmad/custom/skf-rename-skill.toml:
# persistent_facts = ["!file:{project-root}/**/project-context.md"]
persistent_facts = [
"file:{project-root}/**/project-context.md",
]
# Optional post-completion hook: a shell command, run from {project-root}
# in report step 3 with `--result-path=<the per-run result file the shared
# emitter wrote>` appended, before the terminal health-check step. It is
# skipped when the emitter wrote no result file, and a --dry-run never
# reaches it. A hook failure is logged and never fails the rename, which is
# already committed. Use for an audit-log emit, a skill-registry re-index or
# a post-rename notifier.
on_complete = ""
# --- Optional safety scalar ---
#
# A standing approval for headless renames of skills whose
# source_authority is "official". Empty (the default) halts such a run with
# source-authority-blocked unless its invocation passes
# --acknowledge-official, which approves that one run and is the preferred
# answer: a local rename diverges from any registry-published name. Set it
# to "true" (or the TOML boolean true) in a team or personal override to
# let every headless rename of an official skill proceed; each run still
# records the decision in its headless_decisions.
force_source_authority_in_headless = ""
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |