What happened
PR #3381 (feat: improve error messages for Rego compilation failures) was created by the code agent from issue #3345. The issue body, written by human st3penta, used the old project name 'ec-cli' 4 times. The code agent faithfully used 'ec-cli' in the wrapRegoError error message strings, despite the project's root_cmd.go and AGENTS.md header clearly identifying it as 'Conforma CLI'. The review agent caught this on its second run (July 7, inline comment [low] naming). However, the fix agent did not address it after the first bare /fs-fix. The human then manually re-flagged the same naming issue on July 8 with a code suggestion. This required an additional fix iteration to resolve, contributing to the 5-iteration rework cycle.
What could go better
The code agent should prioritize the project's own naming conventions (from AGENTS.md, CLAUDE.md, or root command definitions) over terminology in issue descriptions. Currently, AGENTS.md has no explicit naming guidance. Adding a clear statement about the correct product name would give both the code agent and review agent a definitive reference. Confidence is high that this would prevent recurrence — the code agent demonstrably reads AGENTS.md for build commands and conventions.
Proposed change
Add to the 'Key Conventions' section of conforma/cli's AGENTS.md: 'Product name: This project is "Conforma CLI" (binary name: ec). Do not use the former name "ec-cli" in user-facing strings, error messages, or documentation, even if issue descriptions or existing comments reference the old name.'
Validation criteria
Future code agent PRs that generate user-facing strings (error messages, help text, log output) use 'Conforma CLI' instead of 'ec-cli'. The review agent can reference this AGENTS.md guidance when flagging naming violations, providing a clear rationale rather than relying on cross-referencing root_cmd.go.
Generated by retro agent from #3381
What happened
PR #3381 (feat: improve error messages for Rego compilation failures) was created by the code agent from issue #3345. The issue body, written by human st3penta, used the old project name 'ec-cli' 4 times. The code agent faithfully used 'ec-cli' in the wrapRegoError error message strings, despite the project's root_cmd.go and AGENTS.md header clearly identifying it as 'Conforma CLI'. The review agent caught this on its second run (July 7, inline comment [low] naming). However, the fix agent did not address it after the first bare /fs-fix. The human then manually re-flagged the same naming issue on July 8 with a code suggestion. This required an additional fix iteration to resolve, contributing to the 5-iteration rework cycle.
What could go better
The code agent should prioritize the project's own naming conventions (from AGENTS.md, CLAUDE.md, or root command definitions) over terminology in issue descriptions. Currently, AGENTS.md has no explicit naming guidance. Adding a clear statement about the correct product name would give both the code agent and review agent a definitive reference. Confidence is high that this would prevent recurrence — the code agent demonstrably reads AGENTS.md for build commands and conventions.
Proposed change
Add to the 'Key Conventions' section of conforma/cli's AGENTS.md: 'Product name: This project is "Conforma CLI" (binary name:
ec). Do not use the former name "ec-cli" in user-facing strings, error messages, or documentation, even if issue descriptions or existing comments reference the old name.'Validation criteria
Future code agent PRs that generate user-facing strings (error messages, help text, log output) use 'Conforma CLI' instead of 'ec-cli'. The review agent can reference this AGENTS.md guidance when flagging naming violations, providing a clear rationale rather than relying on cross-referencing root_cmd.go.
Generated by retro agent from #3381