From lisa-rails
Verify JIRA ticket meets standards for epic relationships and description quality
How this command is triggered — by the user, by Claude, or both
Slash command
/lisa-rails:verify <TICKET-ID>jira/This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Use the /lisa-rails:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS
Use the /lisa-rails:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS
npx claudepluginhub codyswanngt/lisa --plugin lisa-rails/verifyRuns verification checks on codebase including types (mypy), lint (ruff), tests (pytest cov), security (pip-audit), secrets, prints, and git status. Outputs summary report with pass/fail and readiness status.
/verifyRebuilds a page from extracted design tokens, pixel-diffs against the live site, and reports a fidelity score. Supports --min for CI gating and --tokens for offline verification.
/verifyVerifies all git-changed files for common mistakes, logic errors, and security issues, outputting per-file summaries with issue counts and severity ratings (CRITICAL, WARNING, INFO).
/verifyRuns comprehensive codebase verification including build, type checks, linting, tests, console.log audit, and git status. Outputs PASS/FAIL report with PR readiness. Supports quick/full/pre-commit/pre-pr modes.
/verifyVerifies implementations or changes using parallel specialized agents with 0-10 grading, full reports across tests/security/quality, and improvement suggestions.
/verifyRun full R verification loop before committing. Checks build, lint, style, test coverage, and code quality.