Skip to content

Optimize Automations Best Practices #296

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ryw merged 1 commit into from
Jan 15, 2026
Merged

Optimize Automations Best Practices #296

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 5 additions & 19 deletions features/automations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -239,25 +239,11 @@ Changes to automations take effect on the next run. Running automations complete

## Best Practices

### Start Simple

Begin with one automation that solves a clear problem. Validate it works well before adding more complexity or creating additional automations.

### Use Templates

Templates are battle-tested starting points. Customize them to fit your workflow rather than building from scratch.

### Be Specific

Vague instructions lead to unpredictable results. Tell the automation exactly what to do, where to post, and how to format output.

### Test First

Use a test repository or Slack channel when setting up new automations. Once validated, switch to production targets.

### Monitor Results

Check run history regularly. If an automation isn't producing useful results, adjust the instructions.
- **Start simple** — Begin with one automation that solves a clear problem before adding complexity
- **Use templates** — Customize battle-tested starting points rather than building from scratch
- **Be specific** — Tell the automation exactly what to do, where to post, and how to format output
- **Test first** — Use a test repository or Slack channel before switching to production targets
- **Monitor results** — Check run history regularly and adjust instructions as needed

---

Expand Down