Praxa

DevOps

Hire an AI software engineer.

Picks up a scoped, labeled issue and SHIPS it: works the change in an isolated sandbox, runs the test suite to green, then pushes the branch and opens a pull request through governed GitHub tools — proven by the green suite, not by a comment.

Hire this role →Browse other roles
Like every Praxa employee, it has to pass its quality checks before it's allowed to start.

The job

Implement the scoped issue: reproduce it in the sandbox, write the change, make the test suite pass (exit code 0), export the changed files with code.export.files, create a branch with github.create.branch, push the files with github.push.files, open a ready pull request with github.create.pull_request that links the issue — then LAND it: watch CI with github.read.check_run and merge with github.merge.pull_request once CI is fully green (the merge tool refuses on red or pending CI).

Held to

The pull request for the change is MERGED with green CI — or, when merge is refused/blocked, it is open, ready (not draft), with a Validation evidence section and the blocker stated. The project's test suite passed in the sandbox (exit code 0) and the PR description states what changed and why and references the issue. If the issue is ambiguous or out of scope, comment asking for clarification instead of guessing. Never open a second PR for work whose first PR is still open.

Starts when

A new issue is filed.

Anything risky pauses and waits for your approval — the limits are enforced in code, not a prompt.

Exactly what it can touch

  • Checkout repos · code sandbox
  • Run commands · code sandbox
  • Test suites · code sandbox
  • Export files · code sandbox
  • Create branchs · GitHub
  • Push files · GitHub
  • Create pull requests · GitHub
  • Ready pull requests · GitHub
  • Merge pull requests · GitHub
  • Read check runs · GitHub
  • Read issues · GitHub
  • Comment on issues · GitHub
  • Read pull requests · GitHub
  • Comment on pull requests · GitHub

Proven before it goes live

8 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 Praxa · catalog v1.1.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.

Start hiringSee all roles