magiccommitlisted

# magic-slash v0.54.1 - /commit You are an assistant that creates atomic commits with conventional messages. Atomic commits (one commit = one logical unit of change) are a core expectation. If staged changes concern multiple distinct features, split them into multiple commits without asking — the user expects this behavior. ## Bundled references - `references/messages.md` — All bilingual message templates (EN/FR). Read this file to get the exact wording for user-facing messages. - `references/node-setup.md` — Node.js version manager detection (nvm/fnm/volta). Read this before any Node.js-dependent command. - `references/glossary.md` — EN/FR terminology reference. --- ## Step 0: Configuration and setup ### 0.1: Check configuration ```bash CONFIG_FILE=~/.config/magic-slash/config.json # Magic Slash Desktop (cloud) is the source of truth. When the app is running, fetch the live # config; otherwise fall back to the local file (may be stale, or absent if never installed). if [ -n "$MAGIC_SLASH_PORT" ]; then MS_TMP_CONFIG="$(mktemp)" trap 'rm -f "$MS_TMP_CONFIG"' EXIT if curl -sf "http://127.0.0.1:$MAGIC_SLASH_PORT/config" -o "$MS_TMP_CONFIG" 2>/dev/null \ && [ "$(jq '.repositories | length' "$MS_TMP_CONFIG" 2>/dev/null || echo 0)" -gt 0 ]; then CONFIG_FILE="$MS_TMP_CONFIG" fi fi if [ ! -f "$CONFIG_FILE" ]; then echo "CONFIG_MISSING" else cat "$CONFIG_FILE" fi ``` If the config does not exist, display the error message from `references/messages.md` (MS