Stats
Actions
Tags
From lisa-rails
This skill should be used when creating JIRA epics, stories, and tasks from code files or descriptions. It analyzes the provided input, determines the appropriate issue hierarchy, and creates issues with comprehensive quality requirements including test-first development and documentation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/lisa-rails:jira-createThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze the provided file(s) and create a comprehensive JIRA hierarchy with all mandatory quality gates.
Analyze the provided file(s) and create a comprehensive JIRA hierarchy with all mandatory quality gates.
Epic → User Story → Tasks (test, implement, document, cleanup)
Test-First: Write tests before implementation Quality Gates: All tests/checks must pass, no SonarCloud violations Documentation: Check existing, update/create new, remove obsolete Feature Flags: All features behind flags with lifecycle plan Cleanup: Remove temporary code, scripts, dev configs
Each issue must clearly communicate to:
Default project: SE (override via arguments) Exclude unless requested: migration plans, performance tests
Execute the analysis and create the complete JIRA structure with proper parent-child relationships.
npx claudepluginhub codyswanngt/lisa --plugin lisa-railsFetches a JIRA issue and distills it into a structured task with acceptance criteria, sprint context, and codebase analysis. Surfaces missing criteria, scope, and risks, and can enrich the JIRA issue with analysis or spawn sub-tickets.
Orchestrates 6-phase workflow (EXPLORE→PLAN→CODE→TEST→FIX→COMMIT) for Jira issues using multi-agent coordination. Manages bugs, stories, tasks, epics with progress tracking and PR linking.