Align one directory with the project's conventions
A directory that predates the current conventions, brought in line with a rule to keep it there.
The ticket
Bring one directory in line with the project's naming and structure conventions.
Acceptance criteria
- File and directory names follow the convention
- Exports follow the project's convention
- A rule enforces the structure for new files
- No behaviour changes
What lands as proof
A structural rule that fails on a non-conforming file, so the convention outlives the ticket.
Why teams defer it
- Renaming files makes history harder to follow, which is a real cost against a cosmetic gain.
- The convention is often unwritten, so it has to be agreed before it can be applied.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: bring one directory in line with the project's naming and structure conventions. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means a rule enforces the convention so it cannot drift back, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.