buildbuddy

Route BuildBuddy troubleshooting and analytics requests to specialized bundled skills.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill routes public BuildBuddy troubleshooting and analytics workflows to the focused BuildBuddy skills bundled in this plugin, providing safe delegation and quick resolution paths.

Core Features & Use Cases

  • Route to specialized skills for invocation troubleshooting, action reproduction, log root cause analysis, flaky-test triage, usage analysis, and invocation comparison.
  • Enforce safety boundaries and MCP/local server routing as described in the plugin guidelines.
  • Provide a unified entry point that quickly classifies requests and forwards to the most specific bundled skill.

Quick Start

Ask the system to route a BuildBuddy invocation issue to the most specific bundled skill.

Frequently Asked Questions about buildbuddy

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

FAQPage Schema
How do I troubleshoot a flaky test in my CI-CD pipeline?

Flaky-test triage is handled by routing your BuildBuddy invocation data to a specialized sub-skill that analyzes test runs to identify the root cause of intermittent failures.

What is the best way to find the root cause of a build failure from logs?

Log root cause analysis is achieved by forwarding your troubleshooting request to a focused skill that parses invocation logs to isolate specific build errors and their origins.

How do I reproduce a failed CI-CD action locally?

Action reproduction is supported by routing the specific invocation details to a bundled skill that provides the exact steps and environment configurations needed to replicate the failure.

Can I compare two BuildBuddy invocations to see what changed?

Invocation comparison is performed by a dedicated sub-skill that analyzes two build runs to highlight differences in actions, dependencies, and execution times.

Does this approach work for analyzing build usage metrics?

Usage analysis is supported by routing your analytics requests to a specific bundled skill that evaluates invocation data to provide insights into build performance and resource consumption.

Is sensitive data exposed when routing troubleshooting workflows?

Safety boundaries are enforced during routing to ensure only safe, non-sensitive data is forwarded to sub-skills, preventing the exposure of confidential build information.