Menu
Run xtask enforcement gates before declaring work complete. Use before finishing any Rust code change.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | spec-check |
| description | Run xtask enforcement gates before declaring work complete. Use before finishing any Rust code change. |
| user-invocable | false |
Before completing any Rust code change, run these checks:
cargo xtask check-no-mod-rs # no mod.rs files
cargo xtask check-actions # action catalog integrity
cargo xtask check-tracing-fields # log field constants used (not literals)
cargo xtask check-error-mapping # HttpError → ToolError mapping complete
cargo xtask check-file-size # no monolithic files
cargo xtask check-env-allowlist # no unauthorized env vars
If any fail, fix before reporting complete. Do not claim success without seeing all checks pass.
Scaffold a new domain module following the spec layout. Creates all required files with correct structure and wires CLI, API, and MCP surfaces.
Authoritative procedure for publishing an MCP server to the official MCP registry at registry.modelcontextprotocol.io — package metadata, server.json schema, authentication, validation, publish, and verification. Preloaded by mcp-publisher.
Stage all current changes, optionally bump project versions, update changelog, commit with an appropriate message, push the current or new feature branch, and then save session documentation. Use when the user asks to quick push, commit and push everything, ship current changes, or run a full git add/commit/push workflow with session capture.
Save the current agent session to an in-repo markdown file with observed metadata, git state, session context, verification evidence, errors, open questions, and next steps. Use when the user asks to save session notes, persist conversation context, create a session log, document the current work, or when another workflow such as quick-push needs post-push session documentation.
Post-cargo-generate setup for a new project. Walks through first-run configuration, domain replacement, and tooling bootstrap.