Guide everyday usage of JCORE CLI commands for WordPress project lifecycle tasks. Use when users ask how to initialize, start, inspect, sync, update, or run commands in JCORE projects, especially when the repository contains a jcore.toml file.
jcore.toml.jcore init, jcore clonejcore start, jcore stop, jcore status, jcore attachjcore run <command>, jcore shelljcore pull [db|plugins|media|all], jcore update [self|<file...>]jcore config, jcore checksum, jcore clean, jcore doctorjcore create block|userjcore init <projectname> --template <template>jcore startjcore statusjcore clone <projectname>jcore start --force (if another JCORE project is already running)jcore attach for logsTo sync the DB/Plugin/Media from upstream, use this command: jcore pull db|plugins|media|all
Only run this command if the user explicitly asks for it.
--template/-t, --branch/-b for init/clone setup--force/-f for overwrite or forced start behaviors--global/-g and --local/-l for config scope--verbose/-v or --debug/-d for investigationsclean all or broad overwrite flows.update <file...>, pull db) before "all".