Codex Delivery Updates for Chat Replies and Requested Documentation
Report results concisely after a coding task and create a written summary when the user requests it as a deliverable.
中文Install in Codex
Use this in a project conversation in Codex. Bring the work outcome, verification results, and the user's requested output format.
- Review `.agents/skills/senior-developer-no-unsolicited-summaries/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/senior-developer-no-unsolicited-summaries/` in your project and save the reviewed file as `.agents/skills/senior-developer-no-unsolicited-summaries/SKILL.md`.
- Start Codex from that project's root, then type `$senior-developer-no-unsolicited-summaries` and select the matching skill.
Example task
Write a chat reply for this fictional coding delivery.
{"change":"align filters on mobile","verified":"390px layout checked","deliverable":"chat only","existing":"CHANGELOG.md"}What to check
Say that mobile filters were aligned and that the layout was verified at `390px`. Keep the deliverable `chat only` and leave `CHANGELOG.md` as it is.
Original SKILL.md on GitHub · Updated
Frequently asked question
When should Codex delivery updates include a separate changelog?
Create a separate changelog when the user asks for it. A chat reply can report the work and the verification results for ordinary handoffs.