Use cases
Automate repository maintenance responsibly
Work through tests, docs, dependencies, warnings, dead code, and issue-selected maintenance with visible boundaries.
Answers: automate repository maintenance with a coding agent · Updated
Use a known punch list for approved maintenance or Quality/Hunt to discover applicable work. Keep each change reviewable, deduplicate findings, and stop when the declared list or convergence condition is satisfied.
Known backlog
Promote approved maintenance from the drafting table into a finite list. Order dependencies first and attach the project gate that proves each result.
- Warnings and lint debt
- Dead code
- Documentation drift
- Dependency upgrades
- Contract and compatibility repairs
Unknown backlog
Quality surveys applicable debt; Automatic Hunt ranks catalog work that fits the available time. Review-first remains read-only until approval.
- Use evidence from the repository.
- Do not manufacture findings to fill time.
- A clean rescan is a successful end.
Maintainer actions stay separate
Nightshift can prepare local changes and receipts. External replies, issue closure, merges, releases, and pushes require explicit authority.
Start with a bounded prompt
This prompt names the outcome and preserves Nightshift’s review boundary. Paste it into the supported coding host from the project you want to change.
Survey this repository for applicable maintenance work, show the evidence and ranking, and wait for my approval before starting fixes.What this workflow does not claim
- Discovery should not manufacture work when the repository's own evidence is clean.
- Issue replies, merges, releases, and pushes remain external maintainer actions.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.