Pin Your CI Environment
Name the runner, versions, caching, and secrets so every CI run is reproducible.
A CI pipeline only helps if its results are reproducible. When you ask Claude to write a workflow, name the concrete environment: which runner, which language version, how dependencies install, and where caching applies. Spell out which secrets the job needs and how it reads them. Leaving these implicit produces a workflow that passes on one machine and fails on the next — pinning them makes every run mean the same thing.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Ship It on Merge
Your CI workflow already lints and tests on pull requests. Now you want a deploy job that runs only when code lands on `main`, building the app and pushing it to your host. The deploy needs an API token that's stored as a repository secret called `DEPLOY_TOKEN`, and you want…