Skip to content

SatcherInstitute/health-equity-tracker / .claude/skills/abandoned

abandoned

Verified

List abandoned BigQuery tables and export JSON (left behind by table renames or dataset moves) in test or prod, and hand the user the delete commands to run by hand. Read-only; never deletes. Use after a datasource rename, for periodic cleanup, or when the user runs /abandoned.

/abandoned

Find leftover BigQuery tables and GCS export JSON that the current pipeline no longer produces, and give the user the commands to delete them. Never run the delete commands yourself. The user reviews and runs them.

The user may pass test or prod (default: both, test first) and optionally a dataset name.

Step 1 — Run the script

From the repo root with the venv active:

source .venv/bin/activate
python scripts/find_abandoned.py --env test > /tmp/abandoned-test.txt 2>&1
python scripts/find_abandoned.py --env prod > /tmp/abandoned-prod.txt 2>&1

Add --dataset <name> when the user named one. It reads BigQuery and GCS via Application Default Credentials and workflow runs via gh, and can take a few minutes for all datasets.

Step 2 — Report

Per environment, give:

  • A short table: dataset, abandoned tables, abandoned JSON groups.
  • Datasets the script skipped (no successful DAG run on record) in one line. They weren't checked.
  • The "Still read by frontend/src" list, called out prominently. These are excluded from the commands because the frontend still requests them, which usually means the frontend points at a renamed or moved dataset and is serving frozen data. Offer to file an issue for each distinct case.

Step 3 — Hand over the commands

Point the user to the # Delete commands section of /tmp/abandoned-<env>.txt and suggest running them dataset by dataset, test before prod. Remind them:

  • Dropped tables are recoverable for 7 days via BigQuery time travel; deleted JSON is not (bucket versioning is off), but any JSON a live table produces is regenerated by rerunning its DAG.
  • gcloud/bq may need gcloud auth login first.

Do not paste hundreds of command lines into chat; summarize counts and point to the file.

finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall