Index of every page on this site: llms.txt
All skills
macro-inc avatar

/rust-validation

@3e0a52a
by Macromacro-inc/macro6.4k stars
606
Run it yourself

Validate Rust work after substantial Rust code changes by running `just check`, `just clippy`, then `just format`. Use before the final response after a significant Rust implementation or cleanup task; batch edits first instead of running after every small change.

Use this Skill: https://skilld.dev/gh/macro-inc/macro/rust-validation

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈70 tokens for metadata: the name and description. ≈301 when used: this file.

How this Skill uses context

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

This Skill turns off automatic use in Claude Code. Its description stays out of the automatic Skill list by default.

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.

Rust Validation

Use this skill when you have changed Rust code or Rust build inputs and are nearing the end of a substantial implementation, refactor, or bug-fix task.

Do not run these commands after every individual edit. Batch related edits first, then validate once at the end of a major work pass or before handing the task back to the user.

Working Directory

Run validation from the repository root. If the root justfile or one of the required recipes is missing, stop and tell the user what prevented validation instead of inventing alternate commands.

Validation Commands

Run these commands one at a time, in this exact order:

just rust-check
just clippy
just format
just hakari

If just rust-check or just clippy fails, do not continue to later commands. Inspect the failure, fix it if it is in scope, then rerun the full sequence starting at just rust-check.

If just format changes files, review the resulting changes before the final response.

Final Response

Briefly report whether validation passed and list the commands that ran. If validation was skipped because no Rust code was changed, or because the user explicitly asked to skip it, say so.

Source: SKILL.md on GitHub

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 alerts20d3 checks · Risk SAFE
  • Gen Agent Trust Hub20d

    The skill automates Rust code validation using standard tools like clippy and format via the `just` command runner. It follows development best practices by using a predefined set of commands and requiring success at each step before proceeding.

  • Socket20d

    No alerts

  • Snyk20d

    Risk: LOW · No issues

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

Last checked against GitHub yesterday.

Activeupdated 4 months ago
disable-model-invocation
true
All 1 allowed tools
Bash Read Edit Glob Grep

README badge

README badge for macro-inc/macro/rust-validation