Repository Setup

Help the user bring a repository to a solid baseline. Prefer understanding and confirmation over spraying every tool into every repo.

Setup is easy to overdo. A marketing site does not need PyPI publishing; a docs repo may not need a heavy test matrix; a monorepo needs different release config than a single library.

• Infer what you can from the tree, then state your working assumptions.
• If repo type, stack, hosting, or whether a step applies is ambiguous, ask before changing files.
• Apply only baselines that fit this repo. Skip or defer the rest and say why.
• Do not invent boilerplate. Leave the repo so a human or agent can operate from README.md and AGENTS.md.

Phase 1: Understand the repository

First understand if it is a greenfield or a brownfield project. In case of greenfield, ask human what he wants to achieve and the purpose of repo.

Inspect the workspace before proposing a plan. Read package manifests, lockfiles, existing CI, README, and directory layout.

Repo shape (pick the best fit; confirm if unsure)