Skip to main content
PT EN
Let's talk
Menu

Explore the resources

A good decision starts with a measure you understand.

Releezy Guardian turns development history into evidence. Explore the logic behind the indicators and how to use them to guide your team.

Discuss my team’s needs Explore the methodology
From review comment to code history

From review comment to code history

Comment checkout.ts Later commit checkout.ts Correspondence in the same file Later commit profile.ts No correspondence in the file No new commit — Outside this calculation scope
A change in the same file.

A later commit touches the commented file. This correspondence contributes to the review effectiveness calculation.

The PR changed. The file did not.

There was a later commit, but in another file. This comment does not receive the same correspondence in the calculation.

No subsequent activity to compare.

Without a later commit, the comment is excluded from this calculation scope. It is not treated as a review with no effect.

From recorded activity to the right conversation.

Three layers help you understand an indicator before acting on it.

The record

Review comments, files and commits produce the observed signal. The history lets you return to the work behind the indicator.

The rule

Effectiveness considers eligible comments and subsequent commits in the same file. Eligibility criteria define which comments enter each scope.

The interpretation

A file change is an activity signal, not proof of causality. Volume, work type and team context complete the picture.

Understand the system. Guide improvement.

An indicator starts an investigation into the work. Understanding the context informs your decision.

  1. Choose a consistent scope

    Define the project, period and activity type. Compare similar situations so that changes are meaningful.

  2. Combine signals

    Look at review effectiveness, code durability and delivery flow. One indicator cannot describe all the work.

  3. Follow up on the action

    Record what changed in team practice and return to the same scope to track progress.

Understand the logic.

Where do rules and AI models fit?

Aggregation rules organize records and calculate indicators. AI models help classify and analyze review comments, adding context to the analysis.

What is included in review effectiveness?

The scope considers comments with an identified file, excluding replies, in PRs with commit file history and at least one later commit. For AI agents, only comments classified as blocking are included; human eligibility does not depend on that classification. File correspondence is applied before aggregation.

How should teams use these insights?

Use the signals to improve the process, share knowledge and calibrate tools. Focus the conversation on what helps the team deliver better, allowing for each project’s context.

Bring a question. Explore the evidence.

See how the Releezy Guardian methodology can help you understand your engineering work.

Discuss my team’s needs