powernode-platform: Skill for Claude Code

Bootstrap Dev Environment

Validate and fix the development environment end-to-end. Follow this process exactly:

Step 1: Check Pending Migrations

cd server && bundle exec rails db:migrate:status

If any migrations are down, run bundle exec rails db:migrate.

Step 2: Audit Seed Files

Use Grep and Read to scan server/db/seeds/ files for:

• class_name: references that don't match actual models in server/app/models/
• Missing foreign_key: paired with class_name:
• Hardcoded UUIDs that may conflict

Report any issues found before proceeding.

Step 3: Run Seeds

cd server && bundle exec rails db:seed 2>&1

If seeds fail:

1. Read the error message carefully
2. Identify the failing seed file and line
3. Read the seed file and the related model
4. Fix the seed file (association name, missing record, validation error)
5. Re-run bundle exec rails db:seed
6. Max 3 attempts — if still failing, stop and report the error

Step 4: Restart Services

Discover the units first. On a module-composed node (dev-cell, ops-hub) they are generated as powernode-<moduleID>-<service>.service, and no @default unit exists: a guessed name fails systemctl silently, which looks exactly like a successful restart. Fall back to the installer's @default name only when discovery finds nothing, which is the plain installer-shape host. Same shape as the deploy skill.

RAILS=$(systemctl list-units 'powernode-*-rails.service' --no-pager --no-legend --plain | awk '{print $1}' | head -1)
SIDEKIQ=$(systemctl list-units 'powernode-*-sidekiq.service' --no-pager --no-legend --plain | awk '{print $1}' | head -1)
sudo systemctl restart "${RAILS:-powernode-backend@default}"
sudo systemctl restart "${SIDEKIQ:-powernode-worker@default}"
systemctl is-active "${RAILS:-powernode-backend@default}" "${SIDEKIQ:-powernode-worker@default}"

Wait 5 seconds, then check status:

sudo scripts/systemd/powernode-installer.sh status

Step 5: Smoke Test