Skip to content

docs(cron): keep PR screening prompt concise #819

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

Closed
shaun-agent wants to merge 3 commits into from
+18 −0
Closed

docs(cron): keep PR screening prompt concise #819

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f50f762
fix(cron): truncate visible trigger messages
shaun-agent May 14, 2026
208e073
Revert "fix(cron): truncate visible trigger messages"
shaun-agent May 14, 2026
3b3d008
docs(cron): keep PR screening prompt concise
shaun-agent May 14, 2026
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
18 changes: 18 additions & 0 deletions docs/cronjob.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,6 +115,24 @@ platform = "slack"
sender_name = "OpsBot"
```

### Concise PR Screening Prompt

Cron job messages are posted into the target chat before the agent runs. Keep operational prompts below the platform message limit, especially Discord's 2,000 character limit.

For OpenAB project screening, use a compact trigger prompt like:

```text
Run OpenAB PR screening once. Use gh only; GH_TOKEN is auth, never gh auth login.

Project: openabdev project 1. Queue: first item in Status=Incoming; if none, first open PR in openabdev/openab with label pending-screening. If no work, reply: no PR-screening work found.

For one item: fetch title, number, URL, body, author, labels, files/checks when relevant. Post/update a GitHub comment marked <!-- openab-project-screening -->. If it came from the project board, move Incoming -> PR-Screening. If it came only from pending-screening, leave board status unless a matching project item exists.

Report sections: Intent, Feat/Fix, Who it serves, Risks, Best-practice comparison if relevant, Options, Recommendation. Be concise and useful to a maintainer.

End the comment with: Agent-ran OpenAB PR screening. Feedback welcome; react thumbs-up if useful.
```

## Helm Deployment

When using the Helm chart, define cronjobs under each agent in `values.yaml`:
Expand Down
Loading