Codex Commit Message Writer for Conventional Commits and Issue References
Turn a supplied Git change into a commit message with a scoped subject, an explanatory body, and an issue footer.
中文Install in Codex
Open your project in Codex. Provide a short change summary or diff and the issue number. Use those materials to try the demonstration skill.
- Review `.agents/skills/commit-message-writer/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/commit-message-writer/` in your project and save the reviewed file as `.agents/skills/commit-message-writer/SKILL.md`.
- Start Codex from that project's root, then type `$commit-message-writer` and select the matching skill.
Example task
Draft a Git commit message from this fictional change. The issue is for reference.
{"type":"docs","scope":"onboarding","change":"document the sample data location","reason":"new contributors could not find the demo input","issue":317}What to check
Start with `docs(onboarding): document the sample data location`. Leave a blank line, explain why contributors need the demo input location, and put `Refs #317` on the final line.
Original SKILL.md on GitHub · Updated
Frequently asked question
Where should the Codex commit message place issue references?
Keep issue references on the final line. The Conventional Commits subject summarizes the change and the body gives the reason.