Cloud AgentsGuides
Guides
Every Cloud Agents guide, each solving one problem end to end with a complete config and the artifact it produced.
Each guide solves one problem end to end: the complete YAML you can deploy, and the output it produces. New to Cloud Agents? Start with the Quick start.
Automate scheduled work
- How to automate your daily standup. Replace the standup ritual with a cron agent that reads yesterday's merged pull requests and writes the summary itself.
- How to prevent documentation drift. Compare documentation against the code every week and open a focused pull request when a concrete claim has drifted.
Answer questions and respond to alerts
- How to answer codebase questions from GitHub, Slack, and Linear. Let anyone ask a question where the work already lives and get an answer from an agent with the code in front of it.
- How to build a custom Slackbot with access to your code. Turn a mention trigger into a team Slackbot that answers from your codebase, opens pull requests, and runs your internal tools.
- How to turn Sentry alerts into root-cause diagnoses. React to alerts with an agent that reads the stack trace, finds the code path, and posts a diagnosis or opens a fix.
Automate pull request upkeep
- How to keep pull request descriptions up to date. Rewrite the description on every push so reviewers read what the branch does now, not what it did on the first commit.
- How to review database migrations before they merge. Put a specialist reviewer on the pull requests that touch migrations, checking locking, backfills, and rollout order.
Set up the environment
- How to give agents the tools and credentials your build needs. Bake your toolchain into a cached image, run setup hooks, and inject credentials so agents can build and test your code.
Teach agents with skills
- How to teach every agent your team's conventions. Write your conventions once as a skill and have every agent load it when the task calls for it.
- How to keep your skills from going stale. Run a daily agent that reads the day's merges and opens a pull request when the code has moved past what your skills claim.
Work with session assets
- How to add screenshots to every pull request. Have agents upload images that outlive the sandbox and paste org-gated links, so a UI change arrives with proof it renders.
Permissions
Each session runs with its own short-lived GitHub token, never a shared credential. Narrow what the token can do per agent in YAML, down to read-only.
How to automate your daily standup
Replace the standup ritual with a cron agent that reads yesterday's merged pull requests and writes the summary itself.