What problem does it solve? Renaming a study in this repository touches many files: the study directory, catalog JSON files, the proposal registry, GitHub proposal issues, References paths, and regenerated PDF/HTML outputs. Doing this manually risks stale links, broken catalogs, and desynchronized portal metadata. This Skill coordinates the entire rename through a single script and a defined checklist. ## Core Features & Use Cases - Script-driven rename: Runs Scripts/_rename_study.py to move the study directory, update catalog rows, sync proposal-registry.json and .proposal-meta.json, and rewrite References paths. - GitHub issue reconciliation: Updates the proposal issue slug and title, or defers updates with --skip-issue until post-merge reconciliation. - Artifact regeneration: Regenerates the study PDF, HTML, and discussion page, with flags like --dry-run, --metadata-only, and --skip-pdf for controlled execution. - Use Case: A contributor needs to shorten a too-long study slug before release. They create a feature branch, dry-run the rename, execute it, update the H1 and Edited-on timestamp, fix cross-study links, and open a study-update PR that passes CI validation. ## Quick Start Ask the assistant to rename the study from the old slug to the new slug using the rename-study workflow, starting with a dry run on a feature branch.
