cmtk is a local-first command line tool for turning common maintainer inputs into Codex-ready workflows.
- Input is read from a file path,
-, or stdin when the path is omitted. - Output defaults to Markdown.
--format jsonwraps the Markdown output in a JSON object for scripts.--format richrenders Markdown in terminals that support Rich formatting.- No network calls, API tokens, repository secrets, or private platform credentials are required for the MVP.
Purpose: triage an issue report into a maintainer checklist and Codex task seed.
Example:
cmtk issue examples/issue-input.mdOutput includes:
- issue type estimate
- priority estimate
- reproducibility checklist
- Codex-ready task brief
- maintainer reply draft
Purpose: summarize a unified PR diff into review risks and a Codex review prompt.
Example:
git diff main...HEAD | cmtk pr -Output includes:
- changed file summary
- additions/deletions count
- initial risk estimate
- review checklist
- Codex review prompt
- visual QA checklist when UI/component files are changed
Purpose: turn a screenshot-driven visual/layout bug report into a scoped repair brief.
Example:
cmtk visual examples/visual-bug.mdOutput includes:
- visual bug goal
- context excerpt
- likely component/CSS/media inspection targets
- screenshot QA checklist
- browser verification steps
- Codex implementation guardrails
Purpose: turn git log text into draft release notes and a pre-tag checklist.
Example:
git log --oneline v0.1.0..HEAD | cmtk release -Output includes:
- features
- fixes
- docs
- other changes
- maintainer release checklist
Purpose: convert maintainer context into a bounded Codex task brief.
Example:
cmtk codex-task examples/issue-input.md --mode implementationOutput includes:
- goal
- context excerpt
- step-by-step Codex instructions
- definition of done
- suggested Codex CLI command
- Heuristic parsing only.
- No GitHub API integration in the MVP.
- No automatic posting, merging, or release publishing.
- Human maintainers review, edit, and approve all outputs.