メニュー
Resolve Bazel labels from terminal output and open the matching BUILD file target with the local bazel-target-open CLI, especially when tmux-fingers selected labels such as //pkg:target or @repo//pkg:target.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Triage this Framework Desktop's Hyprland, CachyOS, SDDM login, Ghostty/Chrome focus, workspace routing, Bluetooth, AirPods, PipeWire, media controls, and local desktop service incidents with live-state checks before changing config.
Triage this Framework Desktop's Hyprland, CachyOS, SDDM login, Ghostty/Chrome focus, workspace routing, Bluetooth, AirPods, PipeWire, media controls, and local desktop service incidents with live-state checks before changing config.
Create GitHub pull requests from the current checkout, including combined commit-and-PR requests. Use when Claude needs to inspect the change, use `draft-commit-message` as the source of truth for the commit message and PR title/body, then push and create a draft or ready PR without a separate wording approval when the user already requested PR creation.
Inspect, instrument, and control Linux Google Chrome through the local Codex Chrome Extension native messaging bridge. Use when Codex needs Chrome tabs, history, navigation, Chrome DevTools Protocol commands, native host manifest/socket troubleshooting, or a Linux browser-control path instead of Chrome DevTools MCP.
Create GitHub pull requests from the current checkout, including combined commit-and-PR requests. Use when Codex needs to inspect the change, use `draft-commit-message` as the source of truth for the commit message and PR title/body, then push and create a draft or ready PR without a separate wording approval when the user already requested PR creation.
Use the local linux-computer-use CLI or MCP server to inspect and safely interact with running Wayland/Hyprland desktop apps through Sky-compatible computer-use tools, grim screenshots, AT-SPI, wtype, ydotool, approvals, and dry-run raw input.
SOC 職業分類に基づく
| name | bazel-target-open |
| description | Resolve Bazel labels from terminal output and open the matching BUILD file target with the local bazel-target-open CLI, especially when tmux-fingers selected labels such as //pkg:target or @repo//pkg:target. |
Use the installed bazel-target-open CLI when the user wants to inspect or open
a Bazel label from terminal output.
Start by verifying the command and local state:
command -v bazel-target-open
bazel-target-open --json doctor
The CLI is local/offline and does not use auth. It resolves labels relative to the current working directory's Bazel workspace.
For read-only inspection, prefer:
bazel-target-open --json resolve //foo:bar
printf '%s\n' '@repo//foo:bar' | bazel-target-open --json resolve
Before live editor actions while debugging, preview the command:
printf '%s\n' //foo:bar | bazel-target-open --json open --dry-run
Live opens are intentional UI actions. Only run bazel-target-open open when
the user asked to open the target or when wiring an interactive tmux-fingers
flow. Inside tmux, it opens a new tmux window; outside tmux, it runs the editor
attached to the current terminal.
Use the raw snippets only for integration work:
bazel-target-open raw regex
bazel-target-open raw tmux-binding --key B
Do not modify .tmux.conf or install/reinstall the CLI unless the user asks for
configuration or setup changes.