pre-push

Run sequential Rust quality checks with cargo and mdbook before pushing.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/langify-org/ws-cli --skill pre-push-langify-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-push
Source: https://github.com/langify-org/ws-cli/tree/main/.claude/skills/pre-push
Command: npx skills add https://github.com/langify-org/ws-cli --skill pre-push-langify-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents broken builds and regressions by executing a sequence of quality checks before pushing changes, ensuring code formatting, linting, tests, and documentation builds are verified.

Core Features & Use Cases

  • Sequential Rust checks: cargo fmt --check, cargo clippy, cargo test, and mdbook build docs (and docs/ja when applicable), with results recorded for each step.
  • Comprehensive results: a final summary table shows pass/fail statuses and, if needed, details from each step to guide fixes before pushing.
  • Use case: ideal for multi-crate Rust projects and team workflows where every push must meet formatting, linting, testing, and documentation standards.

Quick Start

Run the pre-push skill to execute fmt, clippy, test, and docs builds in order before pushing.

Frequently Asked Questions about pre-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run pre-push checks for cargo fmt, clippy, and tests in a Rust project?

To run pre-push checks, execute the skill to sequentially apply cargo fmt --check, cargo clippy, and cargo test across your Rust workspaces, collecting pass/fail results before allowing a push.

What is the best way to automate Rust quality checks before pushing code?

Automating Rust quality checks involves running fmt, clippy, test, and mdbook build docs in sequence, reporting per-step outcomes and a final summary table to prevent broken builds and regressions before pushing.

Can I include mdbook documentation builds in my pre-push verification workflow?

Yes, pre-push verification can include mdbook build docs and docs/ja when applicable, executing these documentation builds alongside cargo fmt, clippy, and test steps to ensure documentation standards are met.

Does this pre-push workflow support multi-crate Rust workspaces?

Yes, this pre-push workflow supports multi-crate Rust projects by collecting results across multiple workspaces, ensuring every crate meets formatting, linting, testing, and documentation standards before a push is allowed.

Why do I need to run quality checks before pushing Rust code changes?

Running quality checks before pushing Rust code prevents broken builds and regressions by verifying code formatting, linting, tests, and documentation builds, ensuring every push meets team standards.

What happens if cargo clippy or cargo test fails during the pre-push sequence?

If cargo clippy or cargo test fails during the pre-push sequence, the final summary table displays the pass/fail statuses and details from each step to guide fixes before the push is allowed.