ampup

Validate and lint code after changes. Use after editing Rust/shell script files, when user mentions compilation errors, linting, clippy warnings, shellcheck issues, or before commits/PRs. Ensures all code passes checks and has zero warnings.

Format Rust and shell script code automatically. Use immediately after editing .rs/.sh files or the install script, when user mentions formatting, code style, or before commits/PRs. Ensures consistent code style following project conventions.

Load relevant coding patterns based on user query or work context. Use when asking about coding patterns, standards, or before implementing code.

Validate pattern doc format against the specification. Use when reviewing PRs, after editing pattern docs, or before commits

Review code changes for bugs, pattern violations, security, and quality. Use when reviewing PRs, code changes, or before commits.

Run targeted tests to validate changes. Use filters to target specific tests when needed.

Generate and validate conventional commit messages with Rust workspace scope rules. Use when user says "commit", "git commit", "/commit", asks for help with commit messages, or requests to amend a commit. Enforces crate-based scoping and validates message accuracy against changesets.

Load relevant feature docs based on user query. Use when user asks about features, functionality, or how things work in the project.

Validate feature doc format against the specification. Use when reviewing PRs, after editing feature docs, or before commits

Report feature maturity and status. Use when asking about project status, feature readiness, or which features are stable/experimental/development

Verify feature doc alignment with implementation. Use when asking about feature implementation status, or to check that documented functionality exists in code and has test coverage