Find and fix broken links and missing files
Links and files that no longer work, fixed, with a scheduled check so they keep working.
The ticket
Find and fix broken links and dead assets, then add a scheduled check.
Acceptance criteria
- Every internal and external link resolves
- Dead assets are replaced or removed
- A scheduled check runs and reports failures to an owner
- External link failures are distinguished from internal ones
What lands as proof
A clean check run plus the schedule that will catch the next rot, since links break after the ticket closes.
Why teams defer it
- Links break silently on somebody else's schedule, long after anybody reviewed the page.
- External links fail intermittently, so a naive check is noisy and gets ignored.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: find and fix broken links and dead assets, then add a scheduled check. 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 every link resolving, the check running on a schedule afterwards, 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.