What problem does it solve? Setting up a repository involves three separate jobs — workflow config, Claude Code hooks, and dependency automation — and running only one leaves the other two silently missing. This Skill coordinates all three generators in the correct order so nothing is skipped and the shared .claude/settings.json file is never clobbered by concurrent writes. ## Core Features & Use Cases - Sequential orchestration: Runs setup-config, then setup-hooks, then setup-deps strictly one at a time, preserving the settings-merge contract between the two generators that write .claude/settings.json. - Combined plan gate: Presents one plan covering every file all three generators would create or modify, and writes nothing before user approval. - Complete run report: Always reports three rows — applied, skipped, declined, or failed — with the reason for every skip, plus a verification step confirming both settings declarations survived. - Use Case: You clone a new repository and say "set up this repo". The Skill walks all three generators in read-only mode, shows you one combined plan, then applies each approved generator in order and reports exactly what ran and why anything was skipped. ## Quick Start Ask the agent to set up this repo from inside the target repository root.
