---
name: local-validation-rust
description: "Use before running local validation in this Rust repository: `cargo fmt`, `cargo clippy`, `cargo test`, or any Cargo build in a worktree. Covers allowing a lint deliberately, when to add the `cargo` Dependabot entry, the shared `CARGO_TARGET_DIR` for worktrees and who deletes it, and switching Release Please to the `rust` release type."
title: local-validation-rust
canonical_url: https://skilld.dev/gh/bydradev/gh-repo-bootstrapper/local-validation-rust
last_updated: 2026-10-30T03:16:22.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install bydradev/gh-repo-bootstrapper/local-validation-rust`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/local-validation-rust`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/bydradev/gh-repo-bootstrapper/local-validation-rust) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/local-validation-rust`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/local-validation-rust --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/local-validation-rust --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Local validation for Rust

If `## Project specifics` in `AGENTS.md` names a repository-owned validation
skill, load it first; where it is narrower, it governs.

The commands to run before pushing are in the `## Tooling` section of `AGENTS.md`. This skill covers the detail behind them.

## Lints

As generated, CI runs Clippy with `-D warnings`, so every warning fails it;
check `.github/workflows/test.yml`, which this repository owns.
If a lint is wrong for this codebase, allow it deliberately (in the `[lints]`
table of `Cargo.toml`, or on the narrowest item with a stated reason) and say
why in the commit or PR; never silence it just to pass CI.

## Dependabot

As generated, `.github/dependabot.yml` covers GitHub Actions only: a new
repository has no `Cargo.toml`, and a `cargo` entry would fail on every run
until one exists. Once the manifest is committed, add a `cargo` ecosystem
entry if the file has none.

## Worktrees

Cargo writes build output to `target/` in each checkout, and a workspace build
can reach gigabytes. In a worktree, set `CARGO_TARGET_DIR` to one fixed
directory for this repository, outside the source tree: `target` inside the
directory that holds this repository's worktrees, for example
`../.worktrees/<repo>/target` from the main checkout. Use it for every Cargo
command in those worktrees. Cargo locks the build directory, so a second build
waits for the first rather than corrupting it. Never copy `target/` into a
verification copy.

That shared directory belongs to the repository's worktrees as a group, not to
any one task. Leave it while any of those worktrees exists; the task that
removes the last one deletes it too. It holds only rebuildable output, so when
disk space is short, deleting it costs a rebuild and nothing else; never
create a per-worktree `target/` instead.

## Versioning

As generated, `release-please-config.json` uses the `simple` release type:
Release Please maintains the changelog, tag, and GitHub release, but does not
edit versions in `Cargo.toml`. For a single published crate, switch it to the
`rust` release type; a multi-crate workspace also needs Release Please's
`cargo-workspace` plugin. Make that change deliberately, once the manifest
exists.

## Sources

- Cargo's build-directory lock (its "waiting for file lock" message): cargo
  1.99.1, where a second `cargo build` printed "Blocking waiting for file
  lock on build directory", checked 2026-10-22.
