mktrue(1)
MKTRUE-SYNC(1)mktrue 0.3.1MKTRUE-SYNC(1)

mktrue sync

NAME

mktrue sync — bring the method up to date

SYNOPSIS

mktrue sync [--write] [--target <name>] [--bench <dir>]

mktrue sync --adopt

mktrue sync --restore

DESCRIPTION

sync brings the files the kit owns up to date with this kit, one file at a time, against the hash recorded when each was written:

  • unchanged here, changed in the kit: updated.
  • changed here, unchanged in the kit: kept.
  • changed in both: a conflict. The kit’s version is written beside the file as a .mktrue-next copy.
  • pinned in .mktrue.json: skipped, and reported.
  • deleted here: reported, and put back only with --restore.

It is a dry run unless --write. It never touches what the repository owns: its own rules sections, state, decisions, plans, logs and source code.

--adopt takes the kit’s version of files that were never under management. sync is also the way into a repository mktrue did not make: the method without the template.

OPTIONS

--write
Write the changes instead of only listing them.
--adopt
Take the kit’s version of files never under management.
--restore
Put back a kit-owned file this repository deleted.
--target <name>
The agent target to render for. The default is claude-code.
--bench <dir>
The kit to render from. The default is the installed kit.
--help
Print the usage of every command.

EXIT STATUS

0true: the plan was printed, or written with --write.
4a decision is needed: a file changed both here and in the kit.

EXAMPLES

The dry run, on a repository already at this kit version.

exit 0
mktrue syncmktrue: sync · kit 0.3.1 → 0.3.1 · dry runmktrue: 0 updates · 0 kept · 0 conflicts · 0 skipped · 0 removedmktrue: true · exit 0

Real output from mktrue 0.3.1, captured with NO_COLOR set.

SEE ALSO