Hide Club

Sets a club to visible = false in the database, creates the corresponding Prisma migration file, and records it in _prisma_migrations.

When to use /hide-club vs /close-club:

• /hide-club — reversible hiding while the club's fate is still open. Use for: duplicate records pending merge, clubs being rehomed as production companies, venues temporarily pulled for data-quality review. Leaves status='active' and closed_at=NULL so the club can be restored by flipping visible back to true. signals establish the venue is gone (Yelp CLOSED, domain dead, platform API 404, no social media activity). Sets status='closed', visible=false, and closed_at=NOW() — the richer metadata lets downstream reporting distinguish "dead" from "hidden pending review."

Usage

/hide-club <club name or ID>

Examples:

• /hide-club 413
• /hide-club BJ's Mobile Drive-In Theater

Step 1: Resolve the Club ID

If the argument is numeric, use it directly as the club ID.

If the argument is a name, look it up:

bash
1"$(git rev-parse --show-toplevel)/apps/scraper/.venv/bin/python3" -c "
2import os, subprocess
3from dotenv import load_dotenv
4scraper_dir = subprocess.check_output(['git', 'rev-parse', '--show-toplevel'], text=True).strip() + '/apps/scraper'
5load_dotenv(scraper_dir + '/.env')
6import psycopg2
7conn = psycopg2.connect(
8    host=os.environ['DATABASE_HOST'],
9    user=os.environ['DATABASE_USER'],
10    password=os.environ['DATABASE_PASSWORD'],
11    dbname=os.environ['DATABASE_NAME'],
12    port=int(os.environ.get('DATABASE_PORT', '5432')),
13    sslmode='require'
14)
15cur = conn.cursor()
16cur.execute(\"SELECT id, name, visible FROM clubs WHERE LOWER(name) LIKE LOWER(%s)\", ('%<name>%',))
17for row in cur.fetchall():
18    print(f'  id={row[0]}  name={row[1]}  visible={row[2]}')
19conn.close()
20"

If multiple matches are returned, ask the user to confirm which club ID to hide. If the club is already hidden (visible=false), inform the user and stop.

Step 2: Hide the Club

bash
1make -C "$(git rev-parse --show-toplevel)/apps/scraper" hide-club ID=<club_id>

This works from any directory within the repo.

This command:

1. Sets visible = false in the database
2. Creates a Prisma migration file at apps/web/prisma/migrations/<timestamp>_hide_<slug>/migration.sql
3. Records the migration in _prisma_migrations

Step 3: Report

Print the migration file path so it can be committed:

Club <id> (<name>) hidden.
Migration: apps/web/prisma/migrations/<migration_name>/migration.sql

If this was invoked as part of a /tusk workflow, the migration file should be committed using tusk commit with the appropriate task ID and criteria.