Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Safely execute rename requests and mass refactoring using file-by-file native edits, semantic AST tools, and optional BTRFS staging verification.
Install Safe Renaming
$ npx skills add r3bl-org/r3bl-open-core --skill safe-renaming -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install r3bl-org/r3bl-open-core safe-renaming --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/safe-renaming .claude/skills/safe-renaming && rm -rf skills-srcUse ~/.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/
Install the "safe-renaming" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/safe-renaming into .claude/skills/safe-renaming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "safe-renaming", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/safe-renamingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add r3bl-org/r3bl-open-core --skill safe-renaming -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install r3bl-org/r3bl-open-core safe-renaming --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/safe-renaming .agents/skills/safe-renaming && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "safe-renaming" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/safe-renaming into .agents/skills/safe-renaming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "safe-renaming", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add r3bl-org/r3bl-open-core --skill safe-renaming -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install r3bl-org/r3bl-open-core safe-renaming --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/safe-renaming .cursor/skills/safe-renaming && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "safe-renaming" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/safe-renaming into .cursor/skills/safe-renaming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "safe-renaming", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/r3bl-org/r3bl-open-core.git --path .agents/skills/safe-renaming--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add r3bl-org/r3bl-open-core --skill safe-renaming -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install r3bl-org/r3bl-open-core safe-renaming --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/safe-renaming .gemini/skills/safe-renaming && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "safe-renaming" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/safe-renaming into .gemini/skills/safe-renaming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "safe-renaming", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install r3bl-org/r3bl-open-core safe-renamingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add r3bl-org/r3bl-open-core --skill safe-renaming -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/safe-renaming .github/skills/safe-renaming && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "safe-renaming" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/safe-renaming into .github/skills/safe-renaming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "safe-renaming", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add r3bl-org/r3bl-open-core --skill safe-renaming -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install r3bl-org/r3bl-open-core safe-renaming --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/safe-renaming .opencode/skills/safe-renaming && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "safe-renaming" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/safe-renaming into .opencode/skills/safe-renaming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "safe-renaming", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
safe-renaming- GitHub stars
- 485
- Token cost
- ~701 tokens
- SKILL.md length
- 292 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Safely execute rename requests and mass refactoring using file-by-file native edits, semantic AST tools, and optional BTRFS staging verification.
- Works in 4 steps: Optional BTRFS Staging Copy → Systematic File-by-File Native Edits → Incremental Validation → …
- Tasks that involve Refactoring
- SKILL.md covers When to Use This Skill, Mandate: No Scripts of Any Kind, Workflow: Safe Staged… and Pitfalls & Safeguards
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Safe Renaming is an agent skill from r3bl-org/r3bl-open-core. Safely execute rename requests and mass refactoring using file-by-file native edits, semantic AST tools, and optional BTRFS staging verification.
Its SKILL.md is about 700 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Refactoring. It works with Rust. The repository describes itself as: TUI framework and developer productivity apps in Rust 🦀. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Refactoring
Example prompts
- “/safe-renaming”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 89db352. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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.
Context cost
Safe Renaming loads about 701 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 292 words of instructions outside code blocks.
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 r3bl-org/r3bl-open-core at commit 89db352, republished under its Apache-2.0 licence (© r3bl-org). 292 words, ~701 tokens.
Download SKILL.mdSave it as
.claude/skills/safe-renaming/SKILL.md (or your agent's skills folder).- name
- safe-renaming
- description
- Safely execute rename requests and mass refactoring using file-by-file native edits, semantic AST tools, and optional BTRFS staging verification.
When to Use This Skill
Activate this skill whenever the user asks for rename requests (e.g., "Rename X to Y across the codebase", "tree-wide rename", "safely rename ..."), or any renaming of variables, fields, functions, parameters, or types across files in the codebase.
Mandate: No Scripts of Any Kind
Scripts of ANY kind (shell scripts like perl, sed, awk, python, bash, fish, or custom/disposable Rust scripts compiled via rustc) are STRICTLY PROHIBITED for performing code refactoring or modifications. All changes must be performed file-by-file using native file-editing tools (replace_file_content / multi_replace_file_content) combined with AST-level semantic tools (rust-analyzer).
Workflow: Safe Staged Refactoring Protocol
To ensure safety during multi-file refactoring, follow this protocol:
Step 1: Optional BTRFS Staging Copy
For large changes, use cp --reflink=auto to create a lightweight, near-instant BTRFS CoW snapshot copy of the workspace in ~/Downloads/rename-staging/.
# Ensure any previous staging directory is clean
rm -rf ~/Downloads/rename-staging
# Create BTRFS reflink clone
cp --reflink=auto -r ~/github/roc ~/Downloads/rename-stagingStep 2: Systematic File-by-File Native Edits
Perform the refactoring file-by-file using native file editing tools (replace_file_content / multi_replace_file_content) and semantic AST tools:
- Search and inspect target occurrences using AST references or grep.
- Carefully apply edits line-by-line or chunk-by-chunk to preserve surrounding rustdoc, formatting, and comments.
- Beware of local variable shadowing (e.g.
let vp_width = ...shadowingvp_width(...)).
Step 3: Incremental Validation
After modifying a batch of 3-5 files, run validation commands:
./check.fish --check
./check.fish --clippy
./check.fish --test
./check.fish --quick-docStep 4: Final Verification
Run full workspace verification on the live repository to confirm 100% clean compilation, zero lint warnings, and all tests passing:
./check.fish --fullPitfalls & Safeguards
- Substrings in Trait/Method names: Ensure identifiers are properly bounded and not partially matching unrelated symbols.
- Module Shadowing: Watch out for local variable names (
let vp_width = ...) that shadow constructor helper functions (vp_width(...)). - Doc Comment Integrity: Ensure plain English prose in doc comments is not inadvertently changed when updating code symbols.
- No Scripts: Never reach for sed/awk/python/rust scripts to automate text replacements.
© r3bl-org, Apache-2.0. 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 .agents/skills/safe-renaming of r3bl-org/r3bl-open-core.
Open the folder on GitHubat commit 89db352
Compare with similar skills
Safe Renaming 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Safe Renaming this skillr3bl-org/r3bl-open-core | 485 | — | ~701 | Automated safety check: Pass | Apache-2.0 | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| RTK Rust Design Patternsrtk-ai/rtk | 83k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| RTK Rust Code Simplifierrtk-ai/rtk | 83k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Rust Hygiene Audittsz-org/tsz | 577 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
RTK Rust Design Patterns
rtk-ai/rtk
Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.
RTK Rust Code Simplifier
rtk-ai/rtk
Reviews RTK's Rust code for over-engineering and verbose patterns, applying idioms like iterator chains and early returns while protecting a specific list of constraints from being simplified away.
Rust Hygiene Audit
tsz-org/tsz
Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues.
Coding Agent
mastra-ai/mastra
Authoring playbook for building agents that write, edit, review, or refactor code.
More from r3bl-org/r3bl-open-core
All 25 skills in this repoAnalyze Log Files
r3bl-org/r3bl-open-core
Analyze log files by stripping ANSI escape sequences first. An agent skill from r3bl-org/r3bl-open-core.
Analyze Performance
r3bl-org/r3bl-open-core
Establish performance baselines and detect regressions using flamegraph analysis.
Check Bounds Safety
r3bl-org/r3bl-open-core
Apply type-safe bounds checking patterns using VPIndex/VPLength types instead of usize.
Release Crate
r3bl-org/r3bl-open-core
Publish a crate release to crates.io with changelog, standalone release notes, git tag, and GitHub release.
Organize Modules
r3bl-org/r3bl-open-core
Apply private modules with public re-exports (barrel export) pattern for clean API design.
Check Code Quality
r3bl-org/r3bl-open-core
Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests.
Related
Works with
Categories
Questions about Safe Renaming
What does Safe Renaming do?
Safely execute rename requests and mass refactoring using file-by-file native edits, semantic AST tools, and optional BTRFS staging verification. Safe Renaming is an agent skill from r3bl-org/r3bl-open-core. Safely execute rename requests and mass refactoring using file-by-file native edits, semantic AST tools, and optional BTRFS staging verification.
When should I use Safe Renaming?
Safe Renaming fits situations like: tasks that involve Refactoring.
How do I install Safe Renaming in Claude Code?
Run `npx skills add r3bl-org/r3bl-open-core --skill safe-renaming -a claude-code`. Or copy the skill folder (.agents/skills/safe-renaming in r3bl-org/r3bl-open-core) into .claude/skills/safe-renaming in your project. Claude Code loads it when a task matches its description.
How do I install Safe Renaming in Codex?
Run `npx skills add r3bl-org/r3bl-open-core --skill safe-renaming -a codex`. Or copy the skill folder (.agents/skills/safe-renaming in r3bl-org/r3bl-open-core) into .agents/skills/safe-renaming in your project. Codex loads it when a task matches its description.
Can I use Safe Renaming 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 r3bl-org/r3bl-open-core --skill safe-renaming -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/safe-renaming, .gemini/skills/safe-renaming, .github/skills/safe-renaming and .opencode/skills/safe-renaming in your project.
What does Safe Renaming need to run?
SKILL.md names no scripts, command-line tools or credentials: Safe Renaming is instructions for the agent only.
Does Safe Renaming access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Safe Renaming 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 Safe Renaming use?
Safe Renaming is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Safe Renaming use?
About 701 tokens (SKILL.md is roughly 2.8k 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 Safe Renaming?
Skills that share tags, products or a category with Safe Renaming: Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Rust Best Practices (farm-fe/farm, 5.6k stars), RTK Rust Design Patterns (rtk-ai/rtk, 83k stars) and RTK Rust Code Simplifier (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Safe Renaming?
r3bl-org (a GitHub organization) maintains it in r3bl-org/r3bl-open-core, which has 485 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 8, 2026.
Source: r3bl-org/r3bl-open-core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.