菜单
Research and implement Buck2 adoption work that bridges Bazel ecosystem expectations, including rules_go or Gazelle comparisons, BCR strategy, Starlark API compatibility, BuildBuddy Workflow bootstrap, release assets, and fixture-backed validation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | buck2-adoption-research |
| description | Research and implement Buck2 adoption work that bridges Bazel ecosystem expectations, including rules_go or Gazelle comparisons, BCR strategy, Starlark API compatibility, BuildBuddy Workflow bootstrap, release assets, and fixture-backed validation. |
Use this in the local Buck2 checkout, usually
${BUCK2_CHECKOUT:-$HOME/work/facebook/buck2}, when the task is about making
Buck2 easier to adopt through Bazel ecosystem compatibility or
BuildBuddy-backed workflow/release improvements. For routine fork stack
refreshes, use buck2-stack-maintainer instead.
git status --short --branch, current branch, remotes, and relevant
fork refs before editing.go test. Use bootstrap/buck2 and local platform overrides when needed.draft-commit-message.fork/main and fork/stack updates, hand off to
buck2-stack-maintainer before rewriting public refs.Return a decision matrix or implementation plan with source evidence, concrete gaps, recommended first tickets, validation commands, and any release or workflow risks.