Issue validation checks whether a pull request fulfills the explicit, verifiable aspects of a linked work issue. An AI review tool interprets the issue, then compares its requirements with the changed code. section 13.3
Evaluate the technique against its practical constraints:
- Use GitHub or GitLab issues as the linked work source; other tracking systems may require duplicating work items as issues. section 13.3
- Write issues with accurate, detailed, interpretable, and verifiable aspects; vague issues can make validation unreliable. section 13.3
- Set team expectations for configuration, learning, participation, and whether validation runs on every pull request or only complex changes. section 13.3
A practical trade-off
A team tracking work on a Jira board would need to duplicate each relevant item in GitHub or GitLab, then maintain enough detail for the tool to verify every requirement. That added effort can outweigh the convenience of automated confirmation. section 13.3
