rust-complete_skill

This skill guides Rust developers through error handling, testing, and logging patterns, demonstrated via includes composition and practical CLI examples.
  • Rust

124

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill dicklesworthstone/meta_skill --skill rust-complete

  • SKILL.md2.1 KB

Overview

This skill provides a comprehensive Rust development checklist and rule set that unites error handling, testing, and logging patterns. It enforces idiomatic Rust, linting, formatting, and minimal unsafe usage while demonstrating composition by merging patterns from standalone modules. The outcome is higher code quality, consistent tooling, and reusable guidance for Rust CLI and library projects.

How this skill works

The skill inspects project code and workflow against a curated ruleset: Rust idioms, clippy lint enforcement, rustfmt formatting, error handling patterns, logging conventions, and a testing checklist. It merges rules and checklists from focused sub-skills so you get a single cohesive guidance set rather than fragmented advice. Use it as a gate or pre-commit checklist, developer reference, or CI step to validate code quality and consistency.

When to use it

  • Bootstrapping a new Rust CLI or library to establish standards
  • Before merging feature branches to enforce linting and formatting
  • Setting up CI checks for clippy, rustfmt, and test coverage
  • Auditing code for unsafe usages and dependency bloat
  • Training newcomers on consistent error handling, logging, and testing patterns

Best practices

  • Run cargo clippy -- -D warnings and cargo fmt as part of CI and local pre-commit hooks
  • Prefer anyhow/thiserror for ergonomic error propagation and add Context where helpful
  • Use tracing for structured logging and instrument functions for observability
  • Keep unsafe blocks minimal, review them explicitly, and document safety invariants
  • Write unit tests for happy and unhappy paths; include edge cases and ensure repeatability

Example use cases

  • Integrate as a CI job that fails on clippy or formatting regressions
  • Use the checklist as a code review template to confirm error handling and logging are present
  • Apply the merged rules to standardize logging prefixes and error contexts across microcommands
  • Embed the testing checklist in new project templates to ensure baseline test coverage
  • Audit a legacy crate: run lints, format, and identify unsafe blocks to plan remediation

FAQ

No. It recommends checks and patterns. It can be wired into CI or tooling that runs cargo fmt or clippy to apply fixes, but the skill itself provides guidance and validations.

Which logging and error libraries does it assume?

It aligns with common, ergonomic choices: tracing for structured logs and anyhow/thiserror for error handling, but the rules are adaptable to other libraries with similar patterns.

How do composed rules work?

Rules from focused modules (error handling, logging, testing) are merged into a single ruleset and checklist so you get consolidated guidance without switching contexts.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational