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.
日本語の概要は準備中です。原文の説明を表示しています。
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).
日本語の概要は準備中です。原文の説明を表示しています。