Keep prompts temporary
Prompts and tool-specific context help an agent work in the moment, but they are not a reliable repository record. Preserve the decisions and evidence that another contributor must be able to audit.
Answer page
Day Shift with Codex or Claude Code: what belongs in the repository
Use coding assistants for implementation; keep the durable implementation contract and evidence in versioned repository files.
Direct answer
Codex or Claude Code can explore, implement, and explain changes. The repository should retain the durable agreement: specification, task scope, target paths, validation, implementation summary, and reconciliation. That makes the workflow portable across agents and reviewers.
Practical guidance
Make the next review decision easier.
Keep contracts versioned
Task definitions make the allowed change boundary and validation visible in code review. They can be read by any coding agent without requiring the original tool, model, or conversation.
Keep judgment explicit
A human still resolves ambiguous product intent, risk, and conflicting evidence. The workflow makes that judgment traceable instead of treating model output as approval.
Verified demo evidence
A public CLI result, not a completion claim.
This command and result are from the website’s checked-in synthetic repository demo. Substitute your own repository paths and validation command when you apply the workflow.
$ day-shift init
Created .day-shift workspace
Next: run day-shift doctorAuthorship and sources
Trace this guidance to maintained product evidence.
- Maintainer
- Tianna McCoy ↗Day Shift maintainer; responsible for the repository-native workflow and release evidence referenced here.
- Last updated
- Tested Day Shift
- v0.1.24
Keep exploring
Follow the next question, not a generic funnel.
What a Human-Agent-Contract Looks Like in a Real Repository
A concrete view of the repository artifacts that make human-agent implementation work traceable and reviewable.
Read nextHow to Make AI Coding-Agent Work Reviewable
Make coding-agent work reviewable with bounded repository artifacts, named validation, and written implementation evidence.
Read nextFAQ
Frequently asked questions about Day Shift's repository-native workflow role.
Read nextFind your answer
Have we answered your question?
Search the answer pages, concept, comparisons, demo, and FAQ without leaving the site.
Search by a problem, workflow step, or tool boundary.