Hephaestus reviews the pull requests, issues, and code reviews your team already writes against the engineering practices you choose. It gives each developer feedback that cites their work and names a next step.

Feedback appears on the work itself, on each developer’s private practice page, and in a conversation. There, developers can ask why, ask for an example, or disagree. Workspace admins can approve feedback before it appears on the work.

Why Hephaestus

Developers learn engineering practices by doing the work and getting feedback on it. That feedback comes from reviewers and experienced colleagues, and their time is scarce. In 37 Apache projects, a 2022 study found that only about a quarter of pull requests received an implicit-mentoring comment. Such a comment explains a suggestion, an instruction, or a way to fix an error. Hephaestus gives feedback on every piece of work it can assess, so experienced people can spend their time where judgment and relationships matter.

Features

• Practices: Start from a curated catalog or write your own. Each states what good work looks like. The catalog covers scoping, issues,…