Stats
Actions
Tags
From probitas
Running and validating Probitas scenarios. Use when executing tests, running scenarios, or debugging test failures.
How this skill is triggered — by the user, by Claude, or both
Slash command
/probitas:probitas-runThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run `/probitas-run` command (or `/probitas-run <selector>` with filter).
Run /probitas-run command (or /probitas-run <selector> with filter).
If project not initialized → run /probitas-init first.
probitas run -s tag:api # Match tag
probitas run -s "!tag:slow" # Exclude tag
probitas run -s user # Match scenario name
/probitas-check for validation errors--verbose or --debug for more outputnpx claudepluginhub probitas-test/claude-plugins --plugin probitasExecutes an existing Playwright E2E suite against a confirmed non-production target and returns a structured run report with pass/fail/flaky counts, durations, and trace artifacts. Requires explicit operator opt-in per session.
Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.