Code automation agent

Runs recurring engineering checks on a schedule. Begin with a concrete goal and define which data the agent may use. A precise output format makes the first result easier to review.

The core stages are dependency checks, release notes, ci monitoring. Run them manually first and preserve examples of a good result in the agent instructions.

Expected output: Recurring engineering tasks completed on time. Review completeness, accuracy, and constraints before enabling a recurring schedule.

After several reliable runs, configure the schedule and notification channel. Keep critical actions behind approval and use execution history to refine instructions and compare quality.