vendor-local

Vendor local Rust crates into Firefox's third_party/rust directory and update Cargo.toml and Cargo.lock.

Updated Mar 14, 2016
One-click install
npx skills add https://github.com/ChunMinChang/dotfiles --skill vendor-local
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vendor-local
Source: https://github.com/ChunMinChang/dotfiles/tree/main/mozilla/firefox/dot.claude/skills/vendor-local
Command: npx skills add https://github.com/ChunMinChang/dotfiles --skill vendor-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers vendor code from a local repository into Firefox's third_party/rust directory, enabling testing of local changes without pushing to upstream.

Core Features & Use Cases

  • Local crate vendoring: copy and integrate a local Rust crate into Firefox's vendored Rust tree.
  • Dependency updates: update Cargo.toml references and the root Cargo.lock accordingly.
  • Workflow support: supports single-commit and multi-commit vendoring, with options for pushing forks or using path dependencies.

Quick Start

Use the vendor-local skill to vendor changes from your local repository into Firefox's third_party/rust directory and update the related Cargo.toml and Cargo.lock.

Frequently Asked Questions about vendor-local

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

FAQPage Schema
How do I vendor local Rust crates into Firefox?

Vendor local Rust crates by copying them into Firefox's third_party/rust directory and updating Cargo.toml and Cargo.lock references. The vendor-local Skill automates this process, supporting single and multi-commit vendoring with optional fork or path dependency strategies for testing local changes before upstream integration.

Can I test local changes to a Rust crate in Firefox without pushing upstream?

Yes. Vendoring local crates into Firefox's third_party/rust directory lets you test changes immediately. The Skill handles repository path discovery, branch or commit selection, cargo updates, and optional try testing workflows.

What's the difference between fork and path dependency strategies for vendoring?

Fork strategy pushes your local crate to a forked repository before vendoring; path dependency strategy references the local path directly in Cargo.toml. Choose based on whether you need a remote reference or prefer local-only testing during development.

Do I need to manually update Cargo.lock when vendoring local Rust crates?

The Skill automates Cargo.lock updates as part of the vendoring process. You specify the branch or commit to vendor, and dependency references are updated accordingly without manual Cargo.lock edits.

What prerequisites are needed before vendoring a local Rust crate into Firefox?

You need the local repository path, Cargo.toml and Cargo.lock accessible in Firefox's tree, knowledge of which branch or commit to vendor, and Cargo installed. The Skill guides repository discovery and branch selection through scripted prompts.

Can vendor-local handle multi-commit Rust crate changes?

Yes. The Skill supports both single-commit and multi-commit vendoring workflows, allowing you to integrate multiple related changes from your local repository into Firefox's vendored Rust tree with coordinated dependency updates.