Index of every page on this site: llms.txt
All skills
bydradev avatar

/local-validation-rust

@20b39bd
Run it yourself

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.

  • 1 file
  • 2.8 KB
  • Updated last month
  • GitHub
Use this Skill: https://skilld.dev/gh/bydradev/gh-repo-bootstrapper/local-validation-rust

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈90 tokens for metadata: the name and description. ≈609 when used: this file.

Description uses 4.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈361 characters, or 4.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 20b39bd. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month

README badge

README badge for bydradev/gh-repo-bootstrapper/local-validation-rust