skills.rest
jmagar
jmagarCOMMUNITY
Explore all skills by this author →
GitHub

spec-check

Automate xtask gate enforcement for Rust changes in CI and local workflows.

Updated Aug 27, 2026
Search Tags:#automation#rust#ci#checks#spec-check#xtask
One-click install
npx skills add https://github.com/jmagar/rust-bin --skill spec-check-jmagar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-check
Source: https://github.com/jmagar/rust-bin/tree/main/.claude/skills/spec-check
Command: npx skills add https://github.com/jmagar/rust-bin --skill spec-check-jmagar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before declaring work complete on a Rust change, enforce xtask gates to run checks and prevent regressions.

Core Features & Use Cases

  • Automated xtask checks: verify required gates (check-no-mod-rs, check-actions, check-tracing-fields, check-error-mapping, check-file-size, check-env-allowlist).
  • CI and local workflow compatibility: ensures consistent gating across development and integration environments.
  • Safety and reliability: prevents premature completion and guides developers toward corrective actions when gates fail.

Quick Start

Before declaring a Rust change complete, run spec-check to ensure all xtask gates pass.

Frequently Asked Questions about spec-check

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

FAQPage Schema
How do I enforce xtask gates before finishing Rust changes?▼

Automating xtask gates for Rust changes requires running checks like check-no-mod-rs, check-actions, and check-tracing-fields before declaring work complete. This prevents regressions by validating required gates across local development and CI pipelines.

What xtask checks should I run to prevent regressions in Rust projects?▼

Required xtask checks include check-no-mod-rs, check-actions, check-tracing-fields, check-error-mapping, check-file-size, and check-env-allowlist. Running these gates validates Rust changes and prevents premature completion when checks fail.

Can I use automated xtask checks in both local development and CI pipelines?▼

Automated xtask checks work across both local development and CI pipeline environments. This ensures consistent gating for Rust changes, preventing regressions regardless of where the validation runs.

What happens when xtask gates fail during Rust development?▼

When xtask gates fail, the automation prevents premature completion and guides developers toward corrective actions. This ensures Rust changes address all check failures before work is declared complete.

Why do I need xtask gates for Rust CI pipelines?▼

Xtask gates enforce required checks before merge in Rust CI pipelines, preventing regressions from incomplete changes. Gates like check-error-mapping and check-env-allowlist validate specific safety and reliability constraints automatically.

Related Skills

Explore More Software Engineering Skills→
lprior-repolprior-repo
1

moon-v2

Orchestrate Rust build and CI/CD workflows with Moon v2 task caching.

Community
Advanced
pko89403pko89403
1

ci-cd-and-automation

Automate GitHub Actions CI/CD pipelines with linting, type checks, tests, and builds.

Community
Advanced
githubgithub
4.9k

console-rendering

Render Go structs into aligned console tables using struct tags.

Official
Basic
lv7devlv7dev

Verification Before Completion

Run verification commands and produce pass/fail status reports.

Community
Basic