From lisa-rails
This skill should be used when verifying that a JIRA ticket meets organizational standards for epic relationships and description quality. It checks epic parent relationships and validates description completeness for coding assistants, developers, and stakeholders.
npx claudepluginhub codyswanngt/lisa --plugin lisa-railsThis skill is limited to using the following tools:
Fetch ticket $ARGUMENTS and verify it meets organizational standards.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Fetch ticket $ARGUMENTS and verify it meets organizational standards.
Rule: Non-bug, non-epic tickets MUST have an epic parent
Verify description adequately addresses:
Coding Assistants: Acceptance criteria, requirements, constraints, I/O Developers: Technical context, integration points, testing, edge cases Stakeholders: Business value, user impact, success metrics, summary
Retrieve ticket details, run both checks, and provide specific improvement recommendations for any failures.