Resets production database with full schema drop. EXTREME CAUTION - deletes all production data. SINGLE SOURCE OF TRUTH for production database reset automation.
Drops all production database schemas to rebuild from migrations. Triggered when you need to reset production data during maintenance windows after backups and approvals.
/plugin marketplace add DarkMonkDev/WitchCityRope/plugin install darkmonkdev-witchcityrope-agents@DarkMonkDev/WitchCityRopeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Purpose: Full database schema reset for PRODUCTION environment - drops all schemas and lets migrations rebuild.
⚠️ EXTREME CAUTION: THIS IS FOR PRODUCTION DATABASE ⚠️
When to Use:
When NOT to Use:
Background Documentation: See /docs/guides-setup/database-setup.md (Production Database Management section) for context and manual procedures.
This skill performs DESTRUCTIVE operations:
public, cms, AND hangfire schemas will be DROPPEDwitchcityrope_production)Prerequisites:
production-deploy skill first)Executable Script: execute.sh
# From project root - with DOUBLE confirmation prompt
bash .claude/skills/database-reset-production/execute.sh
# Skip confirmation prompt (for automation - USE WITH EXTREME CAUTION)
SKIP_CONFIRMATION=true bash .claude/skills/database-reset-production/execute.sh
What the script does:
Script includes MULTIPLE safety warnings - this is a DESTRUCTIVE operation that CANNOT be undone.
If skill fails, manual steps:
Prerequisites: Get DB credentials from server first
Manual schema drop: Connect to database and execute:
DROP SCHEMA IF EXISTS public CASCADE;
CREATE SCHEMA public;
DROP SCHEMA IF EXISTS cms CASCADE;
DROP SCHEMA IF EXISTS hangfire CASCADE;
Then: Restart production containers manually
Cause: PostgreSQL client not installed locally
Solution:
# Ubuntu/Debian
sudo apt install postgresql-client
# macOS
brew install postgresql
Cause: Firewall or network issue
Solution:
ssh witchcity@104.131.165.14Cause: Old migration state or code/DB mismatch
Solution:
production-deploy skillCause: Seed condition not met
Solution:
appsettings.Production.json has SeedData: trueTypical workflow:
production-deploy skillDatabase User: witchcity_production
witchcityrope_production database ONLYConnection String: Uses keyword-value format
Host=...;Port=...;Database=...;Username=...;Password=...;.env.production on serverdatabase-reset-staging skill with enhanced safetydocs/guides-setup/database-setup.mdRemember:
production-deploy skill first to ensure latest code is deployedThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.