What happened
On PR #6613, the PR title references v0.39.0 while the branch name (release-prep/v0.38.0-agents-gate) and both commit messages reference v0.38.0. This mismatch went undetected by both the first review run and the second review run, as well as the human reviewer. The branch and commits consistently say v0.38.0, strongly suggesting v0.39.0 in the title is a typo.
What could go better
The review agent already reads PR metadata for its risk assessment (author, labels, file paths, git history). It does not currently cross-check structured identifiers — version numbers, issue references, or feature names — across the PR title, branch name, and commit messages. For release-prep PRs especially, a version mismatch between the title and branch/commits could confuse searches of PR history or mislead downstream tooling that parses PR titles. Confidence: moderate. This is a minor issue in this specific case (the title doesn't affect workflow behavior), but the class of error — inconsistent version identifiers across PR metadata — could be more impactful on PRs where tooling consumes the title (changelogs, release notes, cross-references).
Proposed change
Add a lightweight metadata-consistency check to the review agent's risk assessment or pre-review triage phase. When the PR title, branch name, or commit messages contain version-like patterns (e.g., v\d+\.\d+\.\d+), semver ranges, or issue references (e.g., #\d+), compare them for consistency. If a version in the title contradicts the branch name or all commit messages, emit a low-severity finding. This check should live in the review agent's skill or sub-agent configuration in fullsend-ai/agents — likely as an addition to the risk-assessment or metadata-analysis step. Keep the check narrow: only flag version-number mismatches, not stylistic differences in phrasing.
Validation criteria
On the next 10 release-prep or version-tagged PRs reviewed by the review agent in fullsend-ai/fullsend, any PR where the title contains a version number that contradicts the branch name or commit messages should produce a low-severity metadata-consistency finding. The check should not produce false positives on PRs where no version numbers appear or where versions are consistent.
Generated by retro agent from fullsend-ai/fullsend#6613
What happened
On PR #6613, the PR title references
v0.39.0while the branch name (release-prep/v0.38.0-agents-gate) and both commit messages referencev0.38.0. This mismatch went undetected by both the first review run and the second review run, as well as the human reviewer. The branch and commits consistently sayv0.38.0, strongly suggestingv0.39.0in the title is a typo.What could go better
The review agent already reads PR metadata for its risk assessment (author, labels, file paths, git history). It does not currently cross-check structured identifiers — version numbers, issue references, or feature names — across the PR title, branch name, and commit messages. For release-prep PRs especially, a version mismatch between the title and branch/commits could confuse searches of PR history or mislead downstream tooling that parses PR titles. Confidence: moderate. This is a minor issue in this specific case (the title doesn't affect workflow behavior), but the class of error — inconsistent version identifiers across PR metadata — could be more impactful on PRs where tooling consumes the title (changelogs, release notes, cross-references).
Proposed change
Add a lightweight metadata-consistency check to the review agent's risk assessment or pre-review triage phase. When the PR title, branch name, or commit messages contain version-like patterns (e.g.,
v\d+\.\d+\.\d+), semver ranges, or issue references (e.g.,#\d+), compare them for consistency. If a version in the title contradicts the branch name or all commit messages, emit a low-severity finding. This check should live in the review agent's skill or sub-agent configuration infullsend-ai/agents— likely as an addition to the risk-assessment or metadata-analysis step. Keep the check narrow: only flag version-number mismatches, not stylistic differences in phrasing.Validation criteria
On the next 10 release-prep or version-tagged PRs reviewed by the review agent in fullsend-ai/fullsend, any PR where the title contains a version number that contradicts the branch name or commit messages should produce a low-severity metadata-consistency finding. The check should not produce false positives on PRs where no version numbers appear or where versions are consistent.
Generated by retro agent from fullsend-ai/fullsend#6613