Example routine
GitHub issue triage
Label, deduplicate, and prioritize new issues so maintainers start the day with a clean queue.
Use this routineSuggested rhythm
Every weekday
0 8 * * 1-5
America/Los_Angeles
Expected result
A morning triage digest: new issues with proposed labels, priorities, duplicates, and drafted first responses.
Built for
Engineering · Support
Works with
- Linear
- GitHub
What the routine does
Review issues opened or updated since the last run in the connected repository {{repository}}. Identify duplicates with links to the original, propose labels and a priority with a one-line justification, and draft a first response for anything missing reproduction steps. Apply labels or post comments only through explicitly approved tools; otherwise leave the proposals in the result for a maintainer to apply.
Inputs
- Repository
{{repository}}The repository whose issues to triage.
Example: acme/web-app
Required MCP capabilities
- Read repository issues
- Comment on issues
Permission boundary
Connections do not grant blanket access. Discover the MCP tools, enable only the capabilities this responsibility needs, and give write-like actions a separate automatic-execution confirmation.
More engineering routines
Weekly
Stale pull request review
Stop finished work from dying in review by naming what blocks each stalled pull request.
Weekly
Weekly error trend review
Notice which errors are actually trending before users report them, without staring at dashboards.
Weekly
Supabase database health review
Turn non-production database diagnostics into a prioritized weekly health brief without exposing customer records or changing state.
Weekly
Jira delivery risk review
Catch plan slippage early by reading Jira boards and Confluence plans instead of waiting for a status meeting.