ask-buddy

Inspect local Bazel and BuildBuddy repository clones to diagnose build issues.

6|Updated Jul 9, 2019
One-click install
npx skills add https://github.com/sluongng/dotfiles --skill ask-buddy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-buddy
Source: https://github.com/sluongng/dotfiles/tree/main/config/codex/plugins/buildbuddy/skills/ask-buddy
Command: npx skills add https://github.com/sluongng/dotfiles --skill ask-buddy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Research BuildBuddy+Bazel issues by inspecting local clones or source history for specified repos.

Core Features & Use Cases

  • Ground issues in local code context from repos: bazelbuild/bazel, buildbuddy-io/buildbuddy, buildbuddy-io/buildbuddy-toolchains, buildbuddy-io/buildbuddy-helm.
  • Survey repository state and version hints (e.g., .bazelversion, .bazeliskrc) to determine the best checkout for analysis.
  • Provide structured outputs with repository state, selected refs, and guidance for next steps.

Quick Start

Run the resolve_context.py helper from this skill directory to inventory local clones and Bazel version hints for the affected workspace.

Frequently Asked Questions about ask-buddy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I root-cause Bazel remote cache or execution failures using local source history?

Diagnosing Bazel remote execution issues involves inspecting local clones of Bazel and BuildBuddy repos to survey repository state and version hints. By probing checked-out commits and local context, you produce evidence-based guidance for remote execution failures.

What is the best way to troubleshoot BuildBuddy BES (Build Event Service) issues from source?

Troubleshooting BuildBuddy BES issues from source requires inspecting local clones of the buildbuddy-io/buildbuddy repository. Surveying repository state and version hints like .bazelversion files selects the best checkout for producing evidence-based BES guidance.

Can I diagnose BuildBuddy Helm deployment problems using local repository clones?

Yes, you can diagnose BuildBuddy Helm deployment problems by inspecting local clones of the buildbuddy-io/buildbuddy-helm repository. Grounding explanations in checked-out commits and local context provides structured outputs with selected refs and next-step guidance.

How do I analyze Bazel toolchain configuration issues from checked-out source commits?

Analyzing Bazel toolchain configuration issues from source involves inspecting local clones of the buildbuddy-io/buildbuddy-toolchains repository. Probing repo state, version hints, and environment hints grounds toolchain analysis in actual checked-out commits for reproducible results.

Why does my Bazel client behave differently across versions when using BuildBuddy?

Bazel client behavior differences across versions with BuildBuddy can be investigated by surveying repository state and version hints like .bazelversion and .bazeliskrc files. Inspecting local clones of bazelbuild/bazel determines the best checkout for producing evidence-based analysis.

Do I need local clones of Bazel repositories to reproduce BuildBuddy analysis?

Yes, local clones of Bazel and BuildBuddy repositories are required for reproducible analysis. Probing repo state, version hints, and environment hints from checked-out commits produces structured outputs with repository state, selected refs, and next-step guidance.