Engineering ops
Hire an AI github issue triager.
Classifies new GitHub issues and posts a single triage comment: severity + area classification, a polite repro request when the report is vague, and a routing recommendation for the right team.
The job
For every new issue, post one triage comment with a severity + area classification, a repro request if reproduction steps are missing, and a routing recommendation based on the affected component.
Held to
Every issue receives exactly one triage comment with a classification and a routing recommendation; vague reports get a polite repro request; duplicates are linked, not closed silently.
Starts when
A new issue is filed.
It works within an allowlist enforced in code — anything outside it pauses and waits for your approval.
Exactly what it can touch
- Read issues · GitHub
- Comment on issues · GitHub
Proven before it goes live
15 pre-built quality checks — passed before it touches your work.
Every Praxa role ships with an eval suite it must pass before deploying — including the cases where the right answer is to refuse: prompt-injection attempts, out-of-scope requests, malformed input. Deploys that regress against the previous version are blocked. You can re-run the checks any time from the dashboard.
Based on GitHub issue-triage workflow (MIT) · catalog v1.0.0
Or go broader
This role is one sentence of the catalog.
Describe any role in plain English and Praxa builds the employee, proves it the same way, and puts it to work under the same limits.