From lisa-rails
Add a Validation Journey section to an existing JIRA ticket by reading the ticket description, understanding the feature, and generating the journey steps and assertions.
npx claudepluginhub codyswanngt/lisa --plugin lisa-railsThis skill uses the workspace's default tool permissions.
Read an existing JIRA ticket, understand the feature or fix it describes, analyze the codebase to determine the verification approach, and append a Validation Journey section to the ticket description.
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.
Read an existing JIRA ticket, understand the feature or fix it describes, analyze the codebase to determine the verification approach, and append a Validation Journey section to the ticket description.
$ARGUMENTS: <TICKET_ID>
TICKET_ID (required): JIRA ticket key (e.g., PROJ-123)JIRA_API_TOKEN environment variable setjira-cli configured (~/.config/.jira/.config.yml)Use the Atlassian MCP or jira-cli to read the full ticket details:
jira issue view <TICKET_ID>
Extract: title, description, acceptance criteria, components, labels, linked tickets.
Run the parser to see if a Validation Journey already exists:
python3 .claude/skills/jira-journey/scripts/parse-plan.py <TICKET_ID> 2>&1
If the parser succeeds and returns steps, the ticket already has a journey. Report this to the user and stop.
Based on the ticket description and acceptance criteria, determine the appropriate verification approach. Stack-specific overrides provide the analysis logic.
Compose the journey following the Validation Journey format with: Prerequisites, Steps (with evidence markers), and Assertions.
Display the drafted Validation Journey to the user and ask for confirmation before appending it to the ticket.
After user approval, use the JIRA REST API to append the Validation Journey to the existing ticket description.
Run the parser again to confirm the journey was added correctly:
python3 .claude/skills/jira-journey/scripts/parse-plan.py <TICKET_ID>