close-club

Close clubs by updating database status and creating a Prisma migration.

Updated May 25, 2024

Search Tags:#workflow #database #migration #prisma #close #data-cleanup #club

Ready to run

npx skills add https://github.com/gioe/laughtrack --skill close-club

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: close-club
Source: https://github.com/gioe/laughtrack/tree/main/.agents/skills/close-club
Command: npx skills add https://github.com/gioe/laughtrack --skill close-club

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Permanently mark defunct clubs as closed in the primary database to prevent them from appearing in active listings, while recording a Prisma migration for audit and version-control purposes.

Core Features & Use Cases

Update the database to set status='closed' and visible=false, and assign closed_at=NOW() to permanently deactivate a venue.
Generate and track a Prisma migration file so schema changes are auditable (and can be deployed via standard pipelines).
Resolve targets by numeric ID or by name, verify current status, and provide a migration path in the report for review.
Use for confirmed-defunct venues; for reversible hiding see /hide-club to simply set visible=false while preserving status.

Quick Start

Invoke the command /close-club with the club's ID or name to permanently close the venue.

Frequently Asked Questions about close-club

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I permanently close a defunct club in a Prisma database?▼

To permanently close a defunct club in a Prisma database, you update the record by setting status='closed', visible=false, and closed_at=NOW(), and generate a Prisma migration file to audit the schema changes.

What is the difference between hiding a club and closing it in a database?▼

Closing a club permanently deactivates it by setting status='closed', visible=false, and closed_at=NOW(), whereas hiding a club only sets visible=false to temporarily remove it from active listings while preserving its status.

How do I resolve a club by name or ID for a database migration?▼

You resolve a club target by providing its numeric ID or exact name, which validates the current status to avoid re-closing an already closed venue and records the migration path for audit review.

Does closing a club automatically create a Prisma migration file?▼

Yes, closing a club automatically creates a Prisma migration file so the database schema changes are auditable and can be deployed via standard version-control pipelines.

What happens if I try to close a club that is already closed?▼

The workflow validates the current status of the club before processing to avoid re-closing an already closed venue, ensuring the database migration only targets active defunct clubs.

How do I report the migration path after closing a club?▼

The close-club workflow reports the action and provides the migration file location for review after updating the database, ensuring the Prisma migration path is recorded for audit purposes.