From bitwize-music
Interactively sets up, edits, shows, validates, or resets ~/.bitwize-music/config.yaml, prompting for artist name, project paths, genres, overrides, and album ideas file.
npx claudepluginhub bitwize-music-studio/claude-ai-music-skills --plugin bitwize-musicThis skill is limited to using the following tools:
**Input**: $ARGUMENTS
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Input: $ARGUMENTS
Route based on argument:
setup or no argument → Interactive first-time setupedit → Edit specific settingsshow → Display current configurationvalidate → Check config for issuesreset → Delete config and start freshYou help users set up and manage their ~/.bitwize-music/config.yaml configuration.
~/.bitwize-music/config.yaml
/configure or /configure setupInteractive first-time setup. Guide user through creating their config.
Steps:
~/.bitwize-music/config.yaml exists~/.bitwize-music/ directory if neededRequired settings to ask:
artist.name - "What's your artist/project name?"paths.content_root - "Where should albums and projects be stored? (e.g., ~/music-projects)"paths.audio_root - "Where should mastered audio files go? (e.g., ~/music-projects/audio)"paths.documents_root - "Where should research documents/PDFs go? (e.g., ~/music-projects/documents)"Optional settings:
5. artist.genres - "What are your primary genres? (comma-separated, or skip)"
6. urls.soundcloud - "SoundCloud profile URL? (or skip)"
Step 5: Overrides Directory (Optional)
Ask:
You can optionally provide a path to a directory containing override files. This is where you can customize workflows and skills without plugin update conflicts.
Override files you can create:
- CLAUDE.md (custom workflow instructions)
- pronunciation-guide.md (artist names, character names)
- explicit-words.md (custom explicit word list)
Default: ~/music-projects/overrides
Enter path (or press Enter to use default):
If user provides path:
paths.overrides: "[user-path]"If user presses Enter (accepts default):
paths.overrides: "~/music-projects/overrides"Step 6: Album Ideas File (Optional)
Ask:
You can optionally provide a path to a file for tracking album ideas. This is managed by the /bitwize-music:album-ideas skill for brainstorming and planning.
Default: ~/music-projects/IDEAS.md
Enter path (or press Enter to use default):
If user provides path:
paths.ideas_file: "[user-path]"If user presses Enter (accepts default):
paths.ideas_file: "~/music-projects/IDEAS.md"Example interaction:
Let's set up your bitwize-music configuration.
What's your artist/project name?
> Neon Circuits
Where should albums and projects be stored?
(This is where your album folders, lyrics, and research will live)
> ~/music-projects
Where should mastered audio files go?
> ~/music-projects/audio
Where should research documents/PDFs go?
> ~/music-projects/documents
What are your primary genres? (comma-separated, or press Enter to skip)
> electronic, synthwave
SoundCloud profile URL? (or press Enter to skip)
> https://soundcloud.com/neon-circuits
Overrides directory path? (press Enter for default: ~/music-projects/overrides)
> [Enter]
Album ideas file path? (press Enter for default: ~/music-projects/IDEAS.md)
> [Enter]
Creating config at ~/.bitwize-music/config.yaml...
✓ Configuration saved!
Your settings:
Artist: Neon Circuits
Content: ~/music-projects
Audio: ~/music-projects/audio
Documents: ~/music-projects/documents
Genres: electronic, synthwave
SoundCloud: https://soundcloud.com/neon-circuits
Overrides: ~/music-projects/overrides (will be used if created)
Ideas File: ~/music-projects/IDEAS.md (will be created when first used)
You're ready to start creating albums!
/configure editEdit specific settings without recreating the whole config.
Steps:
Example:
Current configuration:
artist.name: Neon Circuits
paths.content_root: ~/music-projects
paths.audio_root: ~/music-projects/audio
paths.documents_root: ~/music-projects/documents
artist.genres: [electronic, synthwave]
urls.soundcloud: https://soundcloud.com/neon-circuits
What would you like to change?
/configure showDisplay the current configuration in a readable format.
Steps:
~/.bitwize-music/config.yamlExample output:
bitwize-music Configuration
Location: ~/.bitwize-music/config.yaml
┌─────────────────────┬────────────────────────────────────┐
│ Setting │ Value │
├─────────────────────┼────────────────────────────────────┤
│ artist.name │ Neon Circuits │
│ artist.genres │ electronic, synthwave │
│ paths.content_root │ ~/music-projects │
│ paths.audio_root │ ~/music-projects/audio │
│ paths.documents_root│ ~/music-projects/documents │
│ paths.overrides │ ~/music-projects/overrides │
│ paths.ideas_file │ ~/music-projects/IDEAS.md │
│ urls.soundcloud │ https://soundcloud.com/neon-circuits│
│ generation.service │ suno │
└─────────────────────┴────────────────────────────────────┘
✓ All required settings present
/configure validateCheck the config for issues.
Checks:
Example output:
Validating ~/.bitwize-music/config.yaml...
✓ Config file exists
✓ artist.name: Neon Circuits
✓ paths.content_root: ~/music-projects (exists)
✓ paths.audio_root: ~/music-projects/audio (exists)
✓ paths.documents_root: ~/music-projects/documents (will be created)
✓ paths.overrides: ~/music-projects/overrides (will be used if created)
✓ paths.ideas_file: ~/music-projects/IDEAS.md (will be created when first used)
✓ generation.service: suno
All checks passed!
Or with issues:
Validating ~/.bitwize-music/config.yaml...
✓ Config file exists
✓ artist.name: Neon Circuits
✗ paths.content_root: not set (required)
✓ paths.audio_root: ~/music-projects/audio
✗ paths.documents_root: /invalid/path (directory doesn't exist)
2 issues found. Run /configure edit to fix.
/configure resetDelete config and optionally start fresh.
Steps:
config.yaml.bak~/.bitwize-music/config.yamlExample:
⚠️ This will delete your configuration at ~/.bitwize-music/config.yaml
Current config will be backed up to config.yaml.bak
Are you sure you want to reset? (yes/no)
If yes:
✓ Backed up to ~/.bitwize-music/config.yaml.bak
✓ Deleted ~/.bitwize-music/config.yaml
Config has been reset.
Would you like to set up a new config now? (yes/no)
When creating a new config, use this structure:
# bitwize-music Plugin Configuration
# Generated by /configure
artist:
name: "{artist_name}"
genres:
- "{genre1}"
- "{genre2}"
paths:
content_root: "{content_root}"
audio_root: "{audio_root}"
documents_root: "{documents_root}"
overrides: "{overrides}"
ideas_file: "{ideas_file}"
urls:
soundcloud: "{soundcloud_url}"
generation:
service: suno
config.yaml.bak./projects → /Users/name/projects~ prefix: ~/projects~ in paths for display