スキル debug-tauri
📦
debug-tauri
コンテンツリビジョン r1 高リスク 🌐 ネットワークアクセス📁 ファイルシステムへのアクセス⚙️ 外部コマンド
Tauri WebView アプリをデバッグ
Tauri WebView のバグは、ログ、スクリーンショット、実行時の状態が散在していると診断が困難です。このスキルは、Claude、Codex、Claude Code に、証拠を収集して明確なデバッグレポートを作成するための再現可能なワークフローを提供します。
対応: Claude Codex Code(CC)
インストール前に停止して確認を求めてください。
計画を確認し、ファイルを変更する前にユーザーの明示的な同意を得てください。
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
Review the Skillstore skill "debug-tauri" from https://skillstore.io/skills/8beeeaaat-debug-tauri.md and its manifest at https://skillstore.io/api/skills/8beeeaaat-debug-tauri/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「debug-tauri」を使用しています。 Tauri アプリが空白ウィンドウで開き、開発者が迅速なトリアージを求めています。
期待される結果:
- レポートには、アプリプロセスが実行中かどうかを示し、現在のメモリと CPU の観察結果を記録します。
- スクリーンショットを空白の WebView として説明し、存在する場合は表示されているエラー指標を一覧表示します。
- 最近のログエラーを要約し、まずフロントエンドの初期化と WebView 権限を確認することを推奨します。
「debug-tauri」を使用しています。 メンテナーが macOS のスクリーンショットスクリプトから公式 Tauri プラグインへ移行しています。
期待される結果:
- 移行レビューでは、置き換えるべき古いスクリーンショットコマンドを一覧表示します。
- 新しいプラグインワークフローに必要なログ記録とスクリーンショットの権限を確認します。
- macOS、Windows、Linux 向けのプラットフォーム固有の検証タスクを明示します。
「debug-tauri」を使用しています。 QA エンジニアが失敗した実行からログ、スクリーンショット、WebView 状態を取得しています。
期待される結果:
- デバッグレポートは、視覚的状態、コンソールログ、WebView メタデータ、パフォーマンスの観察結果ごとに証拠を分類します。
- 主な原因と寄与要因を分離し、検証のための具体的な次の手順を提示します。
セキュリティ監査
高リスクv7 • 2026/7/5 バージョン別レポートを開く
Most command-execution and hidden-path alerts are documentation examples or expected local helper-script behavior. Confirmed risk centers on screen capture, temp-stored screenshots or logs, a hidden out-of-package reference, and report workflows that can expose sensitive debugging evidence. No prompt injection attempt or network exfiltration was found in the reviewed files.
11
スキャンされたファイル
2,169
解析済み行数
19
レビュー項目
0
誤検知を無視
確認済みのセキュリティ上の懸念 (47)
高
Screen capture upload
**Status**: Deprecated. Use system `screencapture` command instead.
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
Use system screencapture command instead.
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
Run: screencapture -x -T 0 /tmp/tauri_screenshot.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
See [SCREENSHOTS.md](SCREENSHOTS.md) for screenshot capture methods.
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
- **OS-dependent `screencapture` commands** → `tauri-plugin-screenshots`
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
### Before (macOS screencapture)
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
screencapture -x -T 0 "$output_path"
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
const screenshot = await captureMainWindow();
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
確認済みの47件をすべて表示
高
Screen capture upload
console.log("Screenshot captured");
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
- [ ] Test screenshot capture on all target platforms
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
- **Screenshots**: Works without Screen Recording permission (captures own windows)
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
- macOS screencapture commands
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
## Screenshot Capture
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
Screenshots are captured using `tauri-plugin-screenshots` and optionally copied to `debug-tools/scre
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
## Legacy: macOS screencapture commands
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
### Full screen capture
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
screencapture -x -T 0 /tmp/screenshot.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
screencapture -l <window-id> /tmp/tauri_window.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
### Screenshot cannot be captured
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
- [macOS screencapture man page](https://ss64.com/osx/screencapture.html)
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
# Screenshot Capture Reference
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
Use `tauri-plugin-screenshots` for cross-platform screenshot capture.
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
const screenshot = await captureMainWindow();
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
console.log("Screenshot captured successfully");
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
const screenshots = await captureAllWindows();
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
const monitorScreenshot = await capturePrimaryMonitor();
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
## Legacy: macOS screencapture Command
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
### Full Screen Capture
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
screencapture -x -T 0 /tmp/screenshot.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
screencapture -w /tmp/window_screenshot.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
screencapture -l <window-id> /tmp/tauri_window.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
### Error: Screenshot Not Captured
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
- [macOS screencapture man page](https://ss64.com/osx/screencapture.html) (legacy)
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
### Screenshot Capture Fails
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
# const screenshot = await captureMainWindow();
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
echo " const screenshot = await captureMainWindow();"
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
if ! screencapture -x -T 0 "$output_path" 2>/dev/null; then
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
if screencapture -x -T 0 "$test_file" 2>/dev/null; then
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
check_tool "screencapture" "legacy, optional" ""
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
if pgrep -x "$APP_NAME" > /dev/null && [[ "$OSTYPE" == "darwin"* ]] && screencapture -x -T 0 /tmp/te
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
- **tauri-plugin-screenshots** (v2.0+): Cross-platform screenshot capture
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
Screen capture upload
**Legacy**: capture.sh script (macOS screencapture). See [SCREENSHOTS.md](references/SCREENSHOTS.md)
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
高
Screen capture upload
**Screenshots**: [SCREENSHOTS.md](references/SCREENSHOTS.md) - Capture methods and troubleshooting
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
高
SKILL.md:120-129references/REPORT_TEMPLATE.md:8-18references/REPORT_TEMPLATE.md:20-57references/REPORT_TEMPLATE.md:112-116
Unredacted Debug Evidence Collection
The workflow combines screenshots, process details, console logs, WebView URL, user agent, viewport, and evidence into reports. Without a required redaction step, shared reports can leak sensitive app state, local paths, usernames, tokens, or proprietary UI content.
The cited workflow and template explicitly ask for screenshots, process status, logs, WebView state, and evidence. I found no mandatory redaction guidance before the data is placed into a shareable report.
高
Broad Screenshot Scope Beyond Target Window
The screenshot guidance includes capturing all application windows, the primary monitor, and legacy full-screen screenshots. This broad capture scope can collect unrelated desktop content beyond the target Tauri app.
The cited lines document all-window, monitor, and legacy screen capture paths. The script uses screencapture without limiting capture to a Tauri window.
低
System reconnaissance
osascript -e 'tell application "System Events" to get unix id of first process whose name is "<app-b
The command queries macOS System Events for a process window ID. It is limited to debugging a named app, but it still enumerates local process/window metadata.
低
System reconnaissance
osascript -e 'tell application "System Events" to get unix id of first process whose name is "<app-b
The command queries macOS System Events for a process window ID. It is limited to debugging a named app, but it still enumerates local process/window metadata.
機能レビュー項目 (19)
これらは、このスキルに期待される可能性のある実際のローカル機能であるため、レビューが必要ですが、確認済みの悪意ある動作としてはカウントされません。
高
Path traversal sequence
- [Migration Plan](../../../../.claude/plans/shiny-knitting-squirrel.md)
The Markdown link escapes the skill directory into a hidden .claude planning path. It is not executable, but agents following the reference could be directed outside the packaged skill context.
高
Hidden file access
- [Migration Plan](../../../../.claude/plans/shiny-knitting-squirrel.md)
The reference points to a hidden .claude path outside the skill package. Although it is a Markdown link, it may encourage agents to read private non-packaged files.
中
Temp directory access
Run: screencapture -x -T 0 /tmp/tauri_screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
screencapture -x -T 0 /tmp/screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
screencapture -x -T 0 /tmp/screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
screencapture -w /tmp/window_screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
scrot /tmp/screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
gnome-screenshot -f /tmp/screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
ls -lh /tmp/tauri_console_logs_*.jsonl
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
- `/tmp/tauri_console_logs_[app_name]_[pid].jsonl`
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
- `/tmp/tauri_debug_*.png` (screenshots)
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
test_file="/tmp/screen_test_$$.png"
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
if compgen -G "/tmp/tauri_console_logs_*.jsonl" > /dev/null; then
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
log_file=$(ls -t /tmp/tauri_console_logs_*.jsonl 2>/dev/null | head -1)
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
echo " $(ls -t /tmp/tauri_debug_*.png 2>/dev/null | head -1)"
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
- **macOS**: `/tmp/tauri_console_logs_[app_name]_[pid].jsonl`
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
- **Linux**: `/tmp/tauri_console_logs_[app_name]_[pid].jsonl`
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
中
Temp directory access
- **Windows**: `%TEMP%\tauri_console_logs_[app_name]_[pid].jsonl`
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
リスク要因
🌐 ネットワークアクセス (2)
📁 ファイルシステムへのアクセス (62)
references/IPC_COMMANDS.md:30 references/IPC_COMMANDS.md:30 references/IPC_COMMANDS.md:117 references/LOGGING.md:195 references/LOGGING.md:56 references/LOGGING.md:59 references/LOGGING.md:119 references/LOGGING.md:56 references/LOGGING.md:59 references/LOGGING.md:119 references/LOGGING.md:144 references/MIGRATION.md:487 references/MIGRATION.md:455 references/MIGRATION.md:455 references/MIGRATION.md:487 references/REFERENCE.md:106 references/REFERENCE.md:121 references/REPORT_TEMPLATE.md:10 references/SCREENSHOTS.md:102 references/SCREENSHOTS.md:113 references/SCREENSHOTS.md:125 references/SCREENSHOTS.md:176 references/SCREENSHOTS.md:179 references/TROUBLESHOOTING.md:69 references/TROUBLESHOOTING.md:143 references/TROUBLESHOOTING.md:144 scripts/analyze_logs.sh:55 scripts/analyze_logs.sh:24 scripts/analyze_logs.sh:55 scripts/analyze_logs.sh:67 scripts/analyze_logs.sh:68 scripts/analyze_logs.sh:69 scripts/analyze_logs.sh:70 scripts/analyze_logs.sh:71 scripts/analyze_logs.sh:103 scripts/analyze_logs.sh:109 scripts/analyze_logs.sh:115 scripts/capture.sh:41 scripts/capture.sh:55 scripts/validate_setup.sh:25 scripts/validate_setup.sh:42 scripts/validate_setup.sh:47 scripts/validate_setup.sh:48 scripts/validate_setup.sh:62 scripts/validate_setup.sh:101 scripts/validate_setup.sh:102 scripts/validate_setup.sh:113 scripts/validate_setup.sh:116 scripts/validate_setup.sh:132 scripts/validate_setup.sh:159 scripts/validate_setup.sh:177 scripts/validate_setup.sh:61 scripts/validate_setup.sh:101 scripts/validate_setup.sh:102 scripts/validate_setup.sh:116 scripts/validate_setup.sh:177 scripts/validate_setup.sh:178 SKILL.md:106 SKILL.md:106 SKILL.md:84 SKILL.md:85 SKILL.md:86
⚙️ 外部コマンド (59)
references/LOGGING.md:184-185 references/LOGGING.md:121 references/MIGRATION.md:314-316 references/MIGRATION.md:326-328 references/MIGRATION.md:375-378 references/MIGRATION.md:436-437 references/SCREENSHOTS.md:184 references/SCREENSHOTS.md:185 scripts/analyze_logs.sh:19 scripts/analyze_logs.sh:30 scripts/analyze_logs.sh:40 scripts/analyze_logs.sh:66 scripts/analyze_logs.sh:67 scripts/analyze_logs.sh:68 scripts/analyze_logs.sh:69 scripts/analyze_logs.sh:70 scripts/analyze_logs.sh:71 scripts/analyze_logs.sh:103 scripts/analyze_logs.sh:109 scripts/analyze_logs.sh:115 scripts/analyze_logs.sh:1 scripts/capture.sh:50 scripts/capture.sh:1 scripts/validate_setup.sh:20 scripts/validate_setup.sh:43 scripts/validate_setup.sh:76 scripts/validate_setup.sh:79 scripts/validate_setup.sh:102 scripts/validate_setup.sh:103 scripts/validate_setup.sh:113 scripts/validate_setup.sh:116 scripts/validate_setup.sh:1 SKILL.md:8 SKILL.md:15 SKILL.md:16 SKILL.md:20 SKILL.md:22 SKILL.md:28-37 SKILL.md:37-41 SKILL.md:41-49 SKILL.md:49-52 SKILL.md:52-60 SKILL.md:60-62 SKILL.md:62-70 SKILL.md:70-74 SKILL.md:74-80 SKILL.md:80-84 SKILL.md:84-85 SKILL.md:85-86 SKILL.md:86-88 SKILL.md:88 SKILL.md:92-101 SKILL.md:101-105 SKILL.md:105-106 SKILL.md:106-107 SKILL.md:107-113 SKILL.md:113-116 SKILL.md:116-118 SKILL.md:118-146
検出されたパターン
Screen capture upload×43System reconnaissance×2
監査者: codex 監査履歴を表示 →
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/8beeeaaat-debug-tauri/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/8beeeaaat-debug-tauri?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/8beeeaaat-debug-tauri?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/8beeeaaat-debug-tauri/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/8beeeaaat-debug-tauri.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
8beeeaaat. (2026). debug-tauri security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/8beeeaaat-debug-tauri/audits/7BibTeX形式の引用
@techreport{8beeeaaat-8beeeaaat-debug-tauri-2026,
author = {8beeeaaat},
title = {debug-tauri security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/8beeeaaat-debug-tauri/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "debug-tauri security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "8beeeaaat"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/8beeeaaat-debug-tauri/audits/7"
identifiers:
- type: other
value: "skillstore:8beeeaaat-debug-tauri:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中 68
アーキテクチャ
85
保守性
87
コンテンツ
70
コミュニティ
83
仕様準拠
作成できるもの
WebView レンダリングバグを診断
スクリーンショット、ログ、WebView 状態を収集し、空白画面、レイアウトの失敗、または表示されているランタイムエラーを理解します。
デバッグツール設定を検証
ユーザーの問題を再現する前に、ログ記録、スクリーンショットキャプチャ、権限、プロジェクト構造が準備できているかを確認します。
証拠に基づくバグレポートを作成
プロセスデータ、コンソールでの発見事項、スクリーンショット、状態の観察結果を、開発者向けの構造化されたレポートにまとめます。
これらのプロンプトを試す
自分の Tauri アプリを確認
debug-tauri ワークフローを使用して、私の Tauri アプリが実行中かどうかを確認し、現在の UI 状態をキャプチャして、最初に調査すべき問題を要約してください。
ログとスクリーンショットを分析
最新の Tauri スクリーンショットとプラグインログを分析してください。表示されている UI の問題、最近のエラー、考えられる原因、次の検証手順を特定してください。
プラグイン移行を検証
移行ガイドに照らして、私の Tauri デバッグ設定を確認してください。ログ記録、スクリーンショット、権限、ファイルの場所、残っているレガシー依存関係を確認してください。
デバッグレポートを作成
プロセス状態、スクリーンショットの観察結果、ログ統計、WebView 状態、根本原因分析、優先順位付きの修正から、完全な Tauri デバッグレポートを作成してください。
ベストプラクティス
- 可能な限り、レガシーのプラットフォームスクリプトよりも公式 Tauri プラグインを使用します。
- レポートを共有する前に、スクリーンショット、ログ、ローカルパス、URL、ユーザー名、コマンド引数を編集して伏せます。
- 詳細なデバッグの前に検証を実行し、不足している権限やプラグインによって本来の問題が隠れないようにします。
回避
- アプリウィンドウのキャプチャで十分な場合に、モニター全体をキャプチャしないでください。
- 機密コンテンツを確認する前に、生ログやスクリーンショットを外部システムに貼り付けないでください。
- 最初に設定を確認せずに、プロセスやログファイルが見つからないことをアプリケーションのバグとして扱わないでください。
よくある質問
このスキルは何のデバッグに役立ちますか？
スクリーンショット、ログ、プロセス状態、WebView 状態、レポート用の証拠を収集することで、Tauri WebView の問題のデバッグを支援します。
Tauri v2 が必要ですか？
ドキュメントでは、tauri-plugin-log と tauri-plugin-screenshots を含む、Tauri v2 互換プラグインを想定しています。
Windows と Linux で実行できますか？
推奨されるプラグインワークフローはクロスプラットフォームです。レガシーのキャプチャスクリプトは macOS 専用です。
バグを自動的に修正しますか？
いいえ。開発者が修正を選択して検証できるように、証拠を収集して整理します。
ユーザーはどのデータを保護すべきですか？
共有前に、スクリーンショット、コンソールログ、ローカルファイルパス、URL、プロセスコマンド、WebView 状態を確認する必要があります。
どの AI ツールで使用できますか？
レポートには、Claude、Codex、Claude Code のサポートが記載されています。
開発者情報
作成者
8beeeaaatライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
c4037264bbd363c572662d6154a3ab28f5ca4f53
メンテナンスの新しさ
2026/7/28
利用状況
7 ダウンロード · 223 閲覧
ファイル構成