Ren Labs

Workflows

Pull requests

Ren Code delivers changes as pull requests, not silent commits. You read the diff, you decide what merges — autonomy with an audit trail.

From a request to a PR

  1. Describe the change you want in plain language.
  2. Astra plans the work across the files it actually affects, drawing on its understanding of the repository.
  3. Where it helps, it runs tests and verifies its own work before returning anything.
  4. A pull request is opened on its own branch with a clear description of what changed and why.

What a good pull request includes

  • A summary of the change and the reasoning behind it.
  • A diff scoped to the files the change genuinely touches.
  • Tests that capture intended behavior, where appropriate.
  • Anything you should double-check before merging, stated plainly.

You stay in control

Nothing merges without your review. Pull requests run through your existing branch protections and checks, just like a change from anyone on your team. A confident wrong change is worse than an admitted uncertainty, so Ren Code is built for review rather than blind automation.