What problem does it solve? Setting up a new GitHub repository involves many scattered manual steps — description, topics, labels, default branch, branch protection, merge settings — that are easy to forget or misconfigure, leaving the project's Git Flow and CI rules unenforced. ## Core Features & Use Cases - Repository metadata setup: Derives the description and 3-6 topics from the product definition and applies them with gh repo edit. - Labels and branch flow: Runs the label setup script, creates and publishes develop, and sets it as the default branch so PRs and Dependabot target it correctly. - Branch protection and merge hygiene: Applies protection rules with required check runs (Calidad, Gitleaks), enables squash merge and branch deletion, and explicitly handles the 403 case where private free-plan repos cannot have protection. - Use Case: After instantiating a new project from the template, ask the assistant to configure the repository so labels, the develop branch, protection rules, and merge settings are all in place and documented in the CHANGELOG. ## Quick Start Ask the assistant to configure the GitHub repository for this project, including labels, the develop branch, and branch protection.