# Rust Validation

> 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.

- Skill: `macro-inc/rust-validation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add macro-inc/rust-validation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/macro-inc/rust-validation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: macro-inc (https://skillmd.com/u/macro-inc)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/macro-inc/rust-validation

---


# 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:

```bash
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.