Frequent gates are noisy to type and copy.
Agents and humans may skip them or use inconsistent shortcuts.
Evidence
Cargo supports project-local aliases in .cargo/config.toml under [alias].
Cargo docs say alias values are strings or string arrays and extra CLI args are appended.
Example convention:
cargo x check expands through alias x = "run -p xtask --".
cargo x arch expands through the same alias.
Related spec
SMH-SPEC-SPEC0001 §15 defines xtask command names and requires cargo-only automation.
Expected fix
Add a Cargo alias in .cargo/config.toml for xtask dispatch.
Prefer short, boring alias: x = "run -p xtask --".
Verification
Passed:
cargo x arch
cargo x check
---
id: SMH-ISSUE-R4SEXWVT
type: issue
title: "xtask command invocation is cumbersome"
specs: [SMH-SPEC-SPEC0001]
---
# xtask Command Invocation Is Cumbersome
## Symptom
Required commands use long form:
- `cargo run -p xtask -- check`
- `cargo run -p xtask -- arch`
- `cargo run -p xtask -- lint`
## Impact
Frequent gates are noisy to type and copy.
Agents and humans may skip them or use inconsistent shortcuts.
## Evidence
Cargo supports project-local aliases in `.cargo/config.toml` under `[alias]`.
Cargo docs say alias values are strings or string arrays and extra CLI args are appended.
Example convention:
- `cargo x check` expands through alias `x = "run -p xtask --"`.
- `cargo x arch` expands through the same alias.
## Related spec
- SMH-SPEC-SPEC0001 §15 defines xtask command names and requires cargo-only automation.
## Expected fix
Add a Cargo alias in `.cargo/config.toml` for xtask dispatch.
Prefer short, boring alias: `x = "run -p xtask --"`.
## Verification
Passed:
- `cargo x arch`
- `cargo x check`