Testing Plan for claude-ai-music-skills
Description
Comprehensive testing checklist before marketplace release. ---
Installation
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open the source below and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
Repository README
This is the README for bitwize-music-studio/claude-ai-music-skills, shared by 3 entries
in this directory. It describes the repository, not this entry specifically.
Testing Plan for claude-ai-music-skills
Comprehensive testing checklist before marketplace release.
Prerequisites
- Claude Code installed and working
- Python 3.8+ installed
- Git configured
- A test directory outside the plugin repo (e.g.,
~/test-music-plugin/)
Phase 1: Fresh Install Testing
1.1 Clone Install (Primary Method)
# Create clean test directory
mkdir -p ~/test-music-plugin
cd ~/test-music-plugin
# Clone fresh copy
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git
cd claude-ai-music-skills
# Start Claude Code
claude
**Verify:**
- Claude loads without errors
- CLAUDE.md is recognized (check session start behavior)
- Skills are available (type
/and check menu)
1.2 Plugin Install (Marketplace Method)
# In a different directory (not inside the cloned repo)
cd ~/test-music-plugin
# Add marketplace and install
claude
Then in Claude Code:
/plugin marketplace add bitwize-music-studio/claude-ai-music-skills
/plugin install bitwize-music@claude-ai-music-skills
**Verify:**
- Plugin installs without errors
- Skills appear in
/menu - Can invoke skills (e.g.,
/tutorial help)
Phase 2: Configuration Testing
2.1 Initial Config Setup
cd ~/test-music-plugin/claude-ai-music-skills
# Copy example config
mkdir -p ~/.bitwize-music
cp config/config.example.yaml ~/.bitwize-music/config.yaml
Edit `~/.bitwize-music/config.yaml`:
artist:
name: "test-artist"
paths:
content_root: "~/test-music-plugin/content"
audio_root: "~/test-music-plugin/audio"
documents_root: "~/test-music-plugin/documents"
tools_root: "~/.bitwize-music"
plugin_root: "."
urls:
soundcloud: "https://soundcloud.com/test"
generation:
service: suno
Create directories:
mkdir -p ~/test-music-plugin/content/artists
mkdir -p ~/test-music-plugin/audio
mkdir -p ~/test-music-plugin/documents
mkdir -p ~/.bitwize-music
**Verify:**
- Config loads on session start
- No errors about missing paths
- Claude reports paths correctly
2.2 Path Resolution
In Claude Code, ask: "What are my configured paths?"
**Verify:**
- content_root resolves correctly
- audio_root resolves correctly
- documents_root resolves correctly
- tools_root resolves correctly
Phase 3: Core Workflow Testing
3.1 Tutorial Skill
/tutorial help
**Verify:**
- Help message displays correctly
- Shows all three commands (new-album, resume, help)
/tutorial resume
**Verify:**
- Scans content_root for albums
- Reports "no albums found" (expected for fresh install)
3.2 Album Creation
/tutorial new-album
Walk through Phase 1-2 only (Foundation + Concept):
- Artist: "Test Artist" (new)
- Genre: "electronic"
- Album name: "Test Album"
- Type: "Thematic"
**Verify:**
- Creates artist directory:
{content_root}/artists/test-artist/ - Creates album di
Related Skills
Spec Kit
💫 Toolkit to help you get started with Spec-Driven Development
Testing Webapp Testing
Test local web applications using Playwright for UI verification and debugging
Testing #29
, [#52](https://github.com/affaan-m/everything-claude-code/issues/52), [#103](https://github.com/affaan-m/ever
Testing Fix Issue
by metabase - Addresses GitHub issues by taking issue number as parameter, analyzing context, implementing sol
Testing Pypict Test Design
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for optimized test sui
Testing gstack
| 15,000+ | Garry Tan's exact Claude Code setup: 6 opinionated tools that serve as CEO, Eng Manager, Release M
Testing