personal memory agent
Makefile: CI=true npx --yes for skills add/remove
The trailing -y on `npx skills` goes to the skills CLI, not to npx
itself. On a fresh machine without cached skills@X.Y.Z, npx halts with
an interactive "Ok to proceed?" — blocking the install pipeline and any
coding-agent-driven install. --yes suppresses that prompt; CI=true is
belt-and-suspenders against any other TTY-gated checks in the npm
lifecycle.
Applied to both install-service (fresh-machine path) and uninstall-
service for consistency.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
+2
-2
+2
-2
Makefile
+2
-2
Makefile
···
425
425
;; \
426
426
esac; \
427
427
$(PYTHON) -m think.install_guard install; \
428
-
npx skills add ./skills/solstone -g -a claude-code -y; \
428
+
CI=true npx --yes skills add ./skills/solstone -g -a claude-code -y; \
429
429
$(VENV_BIN)/sol service install --port $(or $(PORT),5015); \
430
430
$(VENV_BIN)/sol service restart; \
431
431
echo "Waiting for service readiness..."; \
···
470
470
fi; \
471
471
$(VENV_BIN)/sol service stop > /dev/null 2>&1 || true; \
472
472
$(VENV_BIN)/sol service uninstall; \
473
-
npx skills remove -g -a claude-code -y solstone; \
473
+
CI=true npx --yes skills remove -g -a claude-code -y solstone; \
474
474
$(PYTHON) -m think.install_guard uninstall
475
475
476
476
uninstall: