Skip to content

armelhbobdad/oh-my-skills / .claude/skills/skf-rename-skill

skf-rename-skill

Verified

Rename a skill across all its versions — transactional copy-verify-delete with platform context rebuild. Use when the user requests to "rename a skill."

FileKindSize
SKILL.mdskill md7.6 KB
customize.tomlconfig3.0 KB
references/execute.mdmarkdown32.7 KB
references/exit-codes.mdmarkdown3.6 KB
references/health-check.mdmarkdown897 B
references/invocation-contract.mdmarkdown4.9 KB
references/report.mdmarkdown9.2 KB
references/select.mdmarkdown31.8 KB
scripts/skf-validate-rename-name.pyscript12.8 KB

references/exit-codes.md

View on GitHub
# Exit Codes — skf-rename-skill

Every HARD HALT in the rename workflow exits with a stable code so headless automators can branch on the failure class without grepping message text. In headless mode each HALT also prints its `SKF_RENAME_SKILL_RESULT_JSON` line through the shared emitter, which derives `exit_code` from `halt_reason` through the schema's `skf-envelope.exit_codes`; this table says where each code is raised:

| Code | Meaning              | Raised by                                                                                    |
| ---- | -------------------- | -------------------------------------------------------------------------------------------- |
| 0    | success              | step 3 (a finished rename, before the step 4 health check); step 1 §8 (the `--dry-run` exit, `status: "dry-run"`) |
| 2    | input-missing / input-invalid | step 1 §4/§5 (headless missing `old_name`/`new_name` arg) → `input-missing`; step 1 §4 (headless `old_name` matches no listed skill) → `input-invalid`; step 1 §5 (headless: the new name fails kebab-case / length / same-as-old; an interactive run asks again) → `input-invalid` |
| 3    | resolution-failure   | step 1 §2 (manifest is malformed JSON) → `manifest-corrupt`; step 1 §3 (no skill SKF generated found anywhere) → `nothing-to-rename` |
| 4    | write-failure        | step 1 §1 (the run-lock, envelope, manifest or inventory helper is missing, or the pre-flight write probe finds the run folder, skills_output_folder or forge_data_folder unwritable), step 1 §2, §3, §5 and §7 (the manifest read, the skill listing, the new-name validator or the version listing prints no JSON), step 1 §4b (the run lock could not be taken), step 1 §6 and §8 (an auto-decision could not be recorded), step 2 §0 (a helper is missing) and step 2 §1 (the run lock could not be renewed) → `write-failed`; step 2 §1 (copy → `copy-failed`); step 2 §2 (inner-dir rename, file content update or the record it writes to the run folder) / §4 (symlink repair) → `write-failed`; step 2 §6 (manifest backup or write → `manifest-write-failed`). step 2 §7 (context-file rewrite) is **best-effort and never halts**: per-file failures are recorded in `context_files_failed` and the rename still succeeds (manifest + disk are canonical; re-run `[EX] Export Skill` to retry). |
| 5    | state-conflict       | step 1 §4a, entered from §3 or §4 (a folder SKF did not generate, one that also holds entries SKF did not generate, or ownership that cannot be checked, in the skill folder or its forge folder, or a forge folder that is a link, is not a folder, or cannot be listed → `not-skf-output`; a flat-layout skill → `flat-layout`); step 1 §5 (name-collision check fails: target name already in use, or `improvement-queue`, or an earlier rename to that name stopped after re-keying the export manifest, whose leftover folders the message names) → `name-collision`; step 1 §6 (source-authority="official" headless without `--acknowledge-official` or `force_source_authority_in_headless`) → `source-authority-blocked`; step 1 §4b (another rename of the same skill holds a run lock that has not gone stale) and step 2 §1 (this run's lock went stale while it waited at a step 1 gate) → `halted-for-concurrent-run`; step 2 §5 (no-trace verification failed: `{old_name}` still present inside the new location, or the verifier exits 2 with no JSON → `verify-failed`; note this rollback is code 5, unlike the copy/write rollbacks at code 4) |
| 6    | user-cancelled       | step 1 §6 (source-authority warning [N]); step 1 §8 confirmation gate `[N]`; any prompt that accepted `cancel`/`exit`/`:q` → `user-cancelled` |
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall