CMU-313 / CMU-313/fall-26-opencode-team-zero
Changes affected by tests are found and explained
Open
@carnegiedude is already working on this.
Since Sep 13, 2026.
enhancement
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Parent User Story: As a student exploring an unfamiliar codebase, I want opencode to identify and explain tests related to the code changes after an edit, so that I can understand how the project's tests validate my implementation.
Estimated effort: 7 hours
Size: M
Dependencies: Associated code and tests
Milestone: Sprint 2
Acceptance criteria:
Possible inputs are identified and explained to the user
Possible outputs are identified and explained to the user
Recently edited code is identified and relevant test processes are explained to the user.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.