Guides
Turn selected GitHub issues into a shift
Import explicitly chosen issues as quoted source, review them, and promote only approved work into the punch list.
Answers: turn selected GitHub issues into coding-agent work · Updated
Nightshift can stage named GitHub issues on the drafting table, but it never searches for issues and never writes back. The owner chooses the URLs or numbers; the shift contract still controls implementation.
Import is intentionally narrow
Provide explicit issue URLs or an owner/repository plus issue numbers. The importer preserves source text for review without treating every request as approved scope.
- No issue search.
- No GitHub write-back.
- No automatic promotion to active work.
- No replacement for maintainer judgment.
Review before promotion
Confirm the issue is current, reproducible, appropriately scoped, and compatible with the project direction. Rewrite the active item as an outcome with local verification rather than copying discussion noise.
- Preserve a link to the source.
- Separate user need from proposed implementation.
- Define the acceptance evidence locally.
Close the engineering loop
Nightshift leaves local commits and receipts. Merging, closing the issue, or posting a reply remains a separate explicit maintainer action.
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.
Import only the GitHub issue URLs I provide, quote them on the drafting table, and wait for me to approve any promotion into the punch list.What this workflow does not claim
- Nightshift never searches for issues and never writes back to GitHub through this workflow.
- Imported issue text is source material, not automatically approved implementation scope.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.