add-buck-dep

Automate adding Rust crate dependencies to Buck2 targets with buckify regeneration.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/rsJames-ttrpg/kerrigan --skill add-buck-dep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-buck-dep
Source: https://github.com/rsJames-ttrpg/kerrigan/tree/main/.claude/skills/add-buck-dep
Command: npx skills add https://github.com/rsJames-ttrpg/kerrigan --skill add-buck-dep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the integration of new Rust crate dependencies into Buck2 targets, ensuring build configurations stay in sync with Cargo manifests.

Core Features & Use Cases

  • Automatically add a dependency to the relevant Cargo.toml files and update Buck targets as part of the build graph.
  • Regenerate and reconcile BUCK files using the buckify process to reflect dependency changes.
  • Apply common build-script fixups for crates that require environment variables or special build steps.

Quick Start

Automatically add a Rust crate dependency to a Buck2 project and refresh the build configuration.

Frequently Asked Questions about add-buck-dep

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

FAQPage Schema
How do I add Rust crate dependencies to Buck2 targets?

To add Rust crate dependencies to Buck2 targets, run cargo add to update Cargo.toml, trigger buckify to regenerate BUCK files, and apply crate-specific fixups to synchronize the build graph with your hybrid Cargo workspace.

How does buckify synchronize BUCK files with Cargo.toml changes?

Buckify synchronizes BUCK files with Cargo.toml changes by regenerating build configurations to reflect newly added Rust crate dependencies, ensuring the Buck2 build graph stays synchronized within a hybrid Cargo workspace setup.

Can I use this automation for a hybrid Cargo workspace setup?

Yes, this automation is specifically designed for hybrid Cargo workspace setups that require buckify regeneration to synchronize BUCK files with Cargo.toml changes after adding new Rust crate dependencies to your Buck2 targets.

What are common build-script fixups for Rust crates in Buck2?

Common build-script fixups for Rust crates in Buck2 involve applying crate-specific adjustments for dependencies that require environment variables or special build steps during the buckify synchronization process.

Why are my Buck2 build configurations out of sync with Cargo manifests?

Buck2 build configurations become out of sync with Cargo manifests when dependencies are added to Cargo.toml without triggering buckify to regenerate BUCK files, requiring automated reconciliation to update the build graph.