rename

name	rename
description	Batch-replace the @lesson-adapter/ package scope with a new scope across the entire codebase. Use this skill when the user says "rename", "change scope", "rebrand", "change the package name", "replace @lesson-adapter", or any variation of wanting to change the npm scope used throughout the monorepo.

Rename

Replace the @lesson-adapter/ package scope with a new scope across the entire codebase.

Step 1: Ask for the New Scope

Ask the user for the new scope. Example: @acme/my-app.

Validate the format: it must match @<scope>/<name>. If invalid, explain the expected format and ask again. Extract the scope prefix (e.g., @acme).

The replacement will change all occurrences of @lesson-adapter/ to @<new-scope>/.

Step 2: Find All References

Use Grep to search for @lesson-adapter/ across the codebase.

Target file types: .json, .ts, .js, .svelte, .md.

Exclude these directories and files:

• node_modules/
• .svelte-kit/
• .turbo/
• build/
• dist/
• .git/
• bun.lock

Show the user the list of files that contain references and the total count.

Step 3: Replace

For each file found, use the Edit tool with replace_all to replace all occurrences of @lesson-adapter/ with @<new-scope>/.

Track which files were changed.

Step 4: Report

1. List all changed files.
2. Remind the user to run bun install to regenerate the lockfile.
3. Suggest running bun turbo typecheck to verify nothing broke.

Edge Cases

• CLAUDE.md contains @lesson-adapter/ references in code examples (e.g., the logging import). These should be updated.
• README.md may contain scope references. Update those too.
• The Dockerfile may contain scope references. Update those too.
• Do NOT rename directories, git repository names, or anything outside of file contents.
• bun.lock will be regenerated by bun install — do not edit it directly.