manage-repo

What problem does it solve? Maintaining a polyglot monorepo means deciding where every configuration row belongs, when a row should be removed, and how to prove a change is safe. This Skill provides placement rules and proof checks for project files, Nx targets, tool versions, CI workflows, and infrastructure declarations across .NET, TypeScript, Python, Java, Swift, and Pulumi. ## Core Features & Use Cases - Placement Rules: Decides which file owns each concern, when a new file is created, and when a row restating a tool default is deleted. - Per-Language References: Covers Nx plugin inference and target defaults, pnpm catalogs and composite TypeScript projects, uv dependency groups and locks, MSBuild central package versions, mise tool rows, Pulumi Automation API, and GitHub Actions workflow forms. - Proof-Based Checks: Requires one run of the project's check target, git diff verification for writers, and baseline comparisons to prove row removals. - Use Case: When adding a new Python script folder to the monorepo, use this Skill to determine it needs a pyproject.toml as a uv workspace member, an Nx target running it from the synced .venv, and a check run as proof. ## Quick Start Use the manage-repo skill to add a new tool row to mise.toml and wire its check target into the root task graph.