rust-quality-gates

$npx mdskill add axone-protocol/contracts/rust-quality-gates

Validates Rust and generated artifacts to ensure quality before committing changes

  • Automatically runs format, lint, test, test-coverage, schema, and docs checks.
  • Deploys locally using a script that can be customized with specific tasks.
  • Decides which gates to run based on the nature of the changes (e.g., message types, response types).
  • Delivers results through script output, allowing users to fix issues before continuing.

SKILL.md

.github/skills/rust-quality-gatesView on GitHub ↗
---
name: rust-quality-gates
description: Repository quality gates for Rust and generated artifacts. Use when validating changes locally or before committing Rust, schema, or documentation updates.
license: BSD-3-Clause
metadata:
  author: axone.xyz
  version: "1.0"
---

# Rust Quality Gates

## Canonical Sequence

Run the full local gate sequence with:

```bash
./.agents/skills/rust-quality-gates/scripts/run-all.sh
```

By default the script runs:

```text
format
lint
test
test-coverage
schema
docs
```

## Running a Subset

Pass explicit task names to run only a subset:

```bash
./.agents/skills/rust-quality-gates/scripts/run-all.sh lint test schema
```

## When to Run Which Gates

- Run the full sequence before finalizing substantial Rust changes.
- Always include `schema` and `docs` when message types, response types, doc comments, or `metadata.json` changed.
- Use the script output as the source of truth. Stop at the first failing gate and fix that issue before continuing.

More from axone-protocol/contracts

SkillDescription
api-doc-commentsGuide for writing Rust doc comments that produce accurate generated contract documentation. Use when editing Instantiate/Execute/Query/Response types or any public schema-facing API.
conventional-commitsGuide for writing conventional commit messages. Use when committing changes, writing commit messages, or reviewing commit history.
cosmwasm-contractAxone contract structure and Abstract SDK patterns. Use when scaffolding or refactoring contracts, deciding layer boundaries, wiring AppContract entrypoints, or adding module metadata and replies.
deploymentAxone deployment workflows with cargo-make, cw-orch, and Abstract. Use when publishing modules, installing them on accounts, running local chain tasks, or inspecting deployments.
doc-generationGuide for regenerating Axone contract schemas and rendered Markdown docs. Use when contract APIs or metadata change, when checking generated-doc drift, or when preparing documentation commits.
rust-contract-domain-modelingDomain-driven modeling patterns for Axone contracts. Use when introducing domain concepts, encoding invariants, or deciding boundaries between domain, handlers, services, gateways, queries, and state.