The trigger defines the workload
A broad event such as every issue update produces noisy, expensive runs. A better trigger names a state transition that already implies action: a labeled bug, a failed dependency check, or a scheduled maintenance window.
Permissions are part of the prompt
An automation should not inherit every capability available to a human operator. Repository access, network tools, secrets, and write permissions need to match the narrow job. A smaller permission surface limits both mistakes and investigation time.
Keep review in the loop
The strongest automation ends with a branch or pull request that follows existing checks. It records what changed, what ran, and what remains uncertain. The agent removes repetitive work; it does not remove the team’s ownership of the result.