verify

name	verify
description	Run verification pipeline after making code changes. Use this skill when the user asks to verify, check, validate, or test their changes, or when you've finished implementing something and need to ensure it works. Also triggers on phrases like "run the checks", "make sure it passes", "verify this works".

Verify Skill

Run the MaaS verification pipeline after code changes.

When to Use

• After implementing a feature or fix
• When the user asks to "verify", "check", "validate", or "test" changes
• Before marking a task complete
• When you want to ensure code quality

Workflow

Run these commands in sequence:

Step 1: Format and Lint

make lint

This auto-fixes formatting and linting issues. If there are unfixable errors, report them and suggest fixes.

Step 2: Quick Unit Tests

make test-unit-fast

Runs unit tests, stopping on first failure. Report any failures with the test name and error message.

Step 3: Optional Extended Checks (if Steps 1-2 pass)

If the above pass and you want deeper verification:

make typecheck   # Type checking with pyright
make security    # Security scan with bandit

Full CI Check

For a complete verification before marking work done:

make ci

This runs lint-check, typecheck, and test-unit.

Reporting

Always summarize results:

• All pass: "All checks passed."
• Failures: List what failed and suggest fixes
• Warnings: Note any warnings that don't block but should be addressed

Example Output

Verification Results:
- make lint: PASSED
- make test-unit-fast: PASSED (93 tests)
- make typecheck: PASSED

All checks passed. Ready to commit.