cdno commit
Manage standalone commitments — dated promises kept as their own notes. To view all commitments
(from every source), use cdno commitments.
cdno commit [OPTIONS] <COMMAND>
Subcommands
| Subcommand | Description |
|---|---|
create | Create an active commitment at commitments/<slug>.md |
done | Mark a commitment completed and archive it |
Both honour --json ({path, message}, non-interactive).
cdno commit create
Create an active commitment note. Optionally attribute it to a project or stewardship.
| Flag | Description |
|---|---|
--title <TITLE> | Commitment title (the slug derives from it). |
--due <YYYY-MM-DD> | Deadline. |
--context <CONTEXT> | Life domain (work, personal, …). |
--project <SLUG> | Optional associated project. |
--stewardship <SLUG> | Optional associated stewardship. |
--var <NAME=VALUE> | Value for a custom template’s prompted variable ([variables.prompt]). Repeatable. See Prompted variables. |
cdno commit create --title "Pay rent" --due 2026-06-01 --context personal
cdno commit create --title "Review Erik's draft" --due 2026-05-20 --context work --project projects/icml-paper
cdno commit done
Mark a commitment completed: stamps status and completed, and moves the note to
commitments/_done/<year>/<slug>.md.
| Flag | Description |
|---|---|
--slug <SLUG> | Commitment slug. |
cdno commit done --slug pay-rent
Related MCP tools
create_commitment, complete_commitment. (View via
get_commitments.)
See also
- Commitments and deadlines.
commitments— the aggregated view.