Stream and search iOS device logs. Use proactively when debugging iOS issues or when user asks to check device logs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Use this skill when the user asks to run the migrated source command ios-logs.
Stream and search logs from a connected iOS device using idevicesyslog.
libimobiledevice installed (brew install libimobiledevice)First, list available devices:
idevice_id -l
This returns UDIDs of devices visible to libimobiledevice. Note: Newer devices using CoreDevice protocol may not appear here.
Stream all logs from a device (replace UDID):
/opt/homebrew/bin/idevicesyslog -u <UDID>
Filter by process name (e.g., ActualChat):
/opt/homebrew/bin/idevicesyslog -u <UDID> -p ActualChat
Filter by message content:
/opt/homebrew/bin/idevicesyslog -u <UDID> -m "error\|warning\|VoIP"
Combine process and message filters:
/opt/homebrew/bin/idevicesyslog -u <UDID> -p ActualChat -m "INF\|error"
Capture logs for a specific duration (e.g., 10 seconds):
/opt/homebrew/bin/idevicesyslog -u <UDID> -p ActualChat &
PID=$!
sleep 10
kill $PID 2>/dev/null
wait $PID 2>/dev/null
Search for VoIP/PushKit logs:
-m "voip\|VoIP\|PushKit\|DidUpdate"
Search for application INFO logs:
-m "INF \[ActualChat"
Search for errors:
-m "error\|Error\|ERR\|Exception"
ActualChat app logs appear as:
Mar 16 18:15:46.425 ActualChat[2869:195195] INF [Namespace.ClassName] Message
If no logs appear:
idevice_id -l-p filter to see all logs아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Delete the `-bak` backup branches that `/prepare-merge` leaves behind, local and on origin, once the work they back up has merged. Use when the user says "remove my bak branches", "clean up bak branches", "delete the backups", or "/clean-bak-branches".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when work on a branch is finished and the next step is a pull request — "create a PR", "open a PR", "push and PR this", "/create-pr" — when a draft PR should be marked ready for review — "mark the PR ready", "undraft it", "it's ready for review" — or right after either has happened and the team has not been told about it yet.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search Google Cloud (GKE) server logs of the DEV environment (dev.voxt.ai). Use when troubleshooting anything that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check GCP logs", "check server logs on dev", or gives a dev.voxt.ai timeline from a client console log.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search Google Cloud (GKE) server logs of the PROD environment. Use when troubleshooting a production incident that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check PROD logs", "check production server logs", or gives a production timeline from a client console log.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
What this project has already learned the hard way, and where any new such fact belongs. Two jobs. (1) Routing: this project keeps NO per-project Claude memories — read this before writing anything down, and pick a durable home from the list here. (2) An index, by area, of non-obvious facts worth knowing before you guess: debugging rigs and measurements that lie, iOS/WebKit and the tethered iPhone, the Windows app, production and deployment, and general codebase traps. Use before setting up a browser- or server-driven debugging session, when a bug reproduces only on iPhone, in Safari or in the Windows app, before changing deployment configuration or reading store/crash data, when something behaves unexpectedly and you are about to guess why, and whenever you are tempted to record a fact for later.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review the EF Core migrations a release (or a PR) carries against how Voxt is deployed: a rolling update whose new pods wait for the migration Job, while old pods keep serving. Use before cutting a release branch, before merging a PR that adds a migration, or when the user says "check the migrations", "are the migrations safe to ship", "expand/contract check", "/migration-release-check". Reports risks; never blocks, edits or runs anything on prod.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.