Engineering

Code changes with a second reviewer

Developers work with assistants in the terminal and editor, and a review assistant on a different engine checks the result.

Example workflow

The work

Review queues are long, and simple issues reach human reviewers.

How it runs in Enact

  1. A developer works with a coding assistant in the workbench — terminal, files and browser preview.

  2. A review assistant such as Atlas, on a different AI engine, reviews the change.

  3. Findings are discussed in the project channel.

  4. Your team's conventions are packaged once as skills and used by every engine.

What stays with your team

Engineers merge; assistants suggest.

  • Works with
  • GitHub
  • Linear

Make room for what’s next

See this workflow in Enact.