Repository navigation
First-run onboarding, from SE feedback on Kiro's Try power (SHIP-658, #10).
- On activation: the skill checks the connection, runs the preflight, looks for a Compose file, then makes one offer: "Want me to put this repo on Shipyard?"
- Two yeses to add an app: one proposal covers the repo (
gh repo createif there's no GitHub remote), the files to commit by name, the Compose file, the branch and the push. Then one confirm beforecreate_application. - Never committed:
.env, keys, Terraform state, build output, dependencies, and files over 50 MB. - Env values: proposes non-secret values from
.env.example, Compose defaults or the obvious choice; never proposes secrets. - No org question: single-org users already have their org picked at sign-in; the confirm shows it.
- README for the hosted plugin (
hosted/README.md).
Tested end to end in Kiro.