check

Run repository quality gates for Rust workspace changes before commits and pushes.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/dmooney/Rundale --skill check-dmooney
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/dmooney/Rundale/tree/main/.agents/skills/check
Command: npx skills add https://github.com/dmooney/Rundale --skill check-dmooney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly verify that the Rundale codebase still meets quality and behavioral expectations, preventing broken changes from slipping through before commit and push.

Core Features & Use Cases

  • Pre-commit quality gates: Runs just check, covering proof evidence, formatting, linting, tests, witness scanning, and doc path validation so failures are caught early.
  • Pre-push verification: Runs just verify to include the full game-harness walkthrough, ensuring gameplay/test walkthrough output remains correct.
  • Actionable CI failure diagnosis: Guides you to rerun failing steps individually and interpret known CI false positives (especially agent-check debt-marker matches in Markdown).

Quick Start

Run the quality gates with the pre-commit workflow by asking to verify the repository status using the top-level command just check from the repo root.

Frequently Asked Questions about check

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

FAQPage Schema
How do I run quality gates for Rust workspace formatting and linting before committing?

Run quality gates for Rust workspace formatting and linting before committing by executing `just check` from the repository root. This validates code formatting, linting, tests, proof evidence, witness scanning, and documentation path correctness to prevent broken changes.

What is the best way to verify a game-harness walkthrough regression check before pushing code?

The best way to verify a game-harness walkthrough regression check before pushing code is to run `just verify`. This pre-push verification includes the full game-harness walkthrough, ensuring gameplay and test walkthrough output remains correct.

Why does CI linting fail on agent-check debt-marker matches in Markdown files?

CI linting fails on agent-check debt-marker matches in Markdown files due to known CI false positives. When diagnosing failures, you should rerun failing steps individually and interpret these specific debt-marker matches as expected false positives rather than actual errors.

How do I diagnose and fix failing Rust quality gate steps in my continuous integration pipeline?

Diagnose and fix failing Rust quality gate steps by rerunning the failing steps individually to isolate the issue. The check process reports pass/fail step results and provides recommended remediation actions for any detected failures.

Does the Rust pre-commit validation workflow include proof evidence and witness scanning checks?

Yes, the Rust pre-commit validation workflow includes proof evidence and witness scanning checks. Running `just check` executes all these repository quality gates, ensuring formatting, linting, tests, and documentation paths are validated before commits.

What steps are required to validate documentation path correctness in a Rust workspace?

To validate documentation path correctness in a Rust workspace, run `just check` from the repository root. This top-level task automatically includes doc path validation alongside formatting, linting, proof evidence, and witness scanning checks.