Recommendation
Use Zapier to create a simple, no-code triage Zap per repo (or a single Zap if you prefer), with Rule Paths for deterministic rules and a catch‑all fallback. Store complex rule sets in an editable Airtable/Google Sheet only if you have many rules. This keeps the flow maintainable by non-devs: paths are visible and easy to update; a spreadsheet/Airtable lets non-technical PMs edit matching rules without changing Zaps.

How the flow works (practical, non-dev steps)
1) Trigger: GitHub “New Issue” (one Zap per repo or one Zap that listens to all three repos).
2) Add “Paths” (one path per common rule): Path conditions = issue title/body contains keyword(s) or labels already present.
3) Actions inside a Path: a) “Add Labels to Issue” (set the label(s)); b) “Update Issue” to set assignee (or “Add Collaborator”); c) optional: “Create Issue Comment” to notify the assignee/triage owner.
4) Default Path: route to an on‑call pool (label “triage-needed”, assign to rotation or triage owner) for manual review.
5) Optional advanced step: if you have many fuzzy rules, add an Airtable lookup (rules table) or a ChatGPT classification step to map issue text to label/assignee.

Decision criteria (choose approach by these factors)
- Few rules (<10 per repo) and want easiest non-dev maintenance: use Zapier Paths. (Requires paid Zapier plan for Paths.)
- Many rules or frequently changing rules: use Airtable/Google Sheet rules table + one Zap that looks up the matching rule and applies it. Better for business users to edit.
- Need advanced semantic classification (not just keywords): add an AI classification step (e.g., ChatGPT via Zapier) but expect cost and occasional tuning.
- Budget/scale: Paths are simplest but require paid Zapier. Airtable+Zapier adds small cost but centralizes rules.

Best-for / Avoid-if
Best for: teams with a few deterministic triage rules, non-dev maintainers, three repos with steady volume.
Avoid if: you need high-quality semantic triage for hundreds of issue types (use a data/ML solution or engineering help instead).

Practical checklist to implement
- Create a GitHub token with repo access and connect GitHub in Zapier. (Keep token in a secure password manager.)
- Make one Zap (or one per repo): Trigger = New Issue. Test with a real issue.
- Add Paths for your top 6–12 rules (title/body contains “bug”, “security”, “docs”, etc.).
- For each Path: Add Labels, Update Assignee, and add Comment notification. Test each path.
- Add Default Path that labels “triage-needed” and assigns to a human rotation.
- (Optional) Build a rules table in Airtable/Google Sheets if you expect many rules; add a Lookup step to select label/assignee.
- Document the rules table and who can edit it; train the PMs on how to add/modify rules.

Notes on maintenance, permissions, and cost
- Zap Paths require a paid Zapier plan. Airtable lookups may require a paid Zapier task allowance. AI classification increases running cost. Choose based on team size, rule count, and budget.
- Keep triage rules minimal and make the default conservative (assign to humans) to avoid misclassification.

If you want, I can draft: a) an example Path list of 8 starter rules for your repos, or b) an Airtable schema and the Zap steps to look up rules. CTA: use Zapier to build the Zaps (zapier).

Compare Zapier and Make