verify

The Verify skill is an automated quality assurance agent designed for Rust developers who require a strict, repeatable pre-commit verification workflow. By orchestrating a sequential pipeline of essential Rust tooling, this agent ensures that code changes are not only functional but also adhere to idiomatic standards and project-specific linting rules before they are even considered for review or integration. It acts as an autonomous gatekeeper that identifies regressions and style violations early in the development lifecycle.

• Executes full cargo test suites to validate logic and system integrity.

• Runs cargo clippy across all targets and features with strict warning enforcement.

• Performs cargo fmt checks to ensure consistent, readable code style across the entire repository.

• Implements a self-healing logic that attempts to resolve build or test errors automatically by analyzing diagnostic output.

• Retries failed steps after automated fixes, up to a maximum of three attempts, before escalating to human intervention.

• Triggers a subsequent code review process immediately upon successful verification, streamlining the transition from development to peer feedback.

• This tool is specifically intended for developers working in environments where automated code quality is a prerequisite for pull requests or commits.

• Input requirements include a standard Rust workspace or package structure utilizing the cargo toolchain.

• Output consists of terminal-based status logs indicating the success or failure of each stage, alongside automated git-compatible fixes when applicable.

• Constraints include a requirement for local environmental access to the Rust compiler and toolchain (rustc, cargo).

• For optimal performance, ensure that development environments are configured with the necessary dependencies for all project features to avoid false-positive failures during the clippy analysis phase.

• The self-healing loop is best utilized in scenarios involving common linting violations or standard test failures; complex logical errors should still be managed through traditional debugging workflows.