From prism-devtools
Jira integration for issue search, context fetching, and story planning with templates. Use when: user mentions issue keys (PLAT-123, JIRA-456), asks to "search backlog", "find stories", "look for bugs", needs "ticket details", wants to "plan a story", "create a story", "write a story", "user story for", mentions "jira template", "story template", or asks about acceptance criteria.
npx claudepluginhub resolve-io/.prismThis skill uses the workspace's default tool permissions.
Read-only Jira integration using Python scripts for reliable issue fetching and search. Also provides story templates for planning new work.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Provides patterns for autonomous Claude Code loops: sequential pipelines, agentic REPLs, PR cycles, de-sloppify cleanups, and RFC-driven multi-agent DAGs. For continuous dev workflows without intervention.
Applies NestJS patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production TypeScript backends with project structure and bootstrap examples.
Read-only Jira integration using Python scripts for reliable issue fetching and search. Also provides story templates for planning new work.
python "${CLAUDE_PLUGIN_ROOT}/skills/jira/scripts/jira_fetch.py" PLAT-123
python "${CLAUDE_PLUGIN_ROOT}/skills/jira/scripts/jira_search.py" "project = PLAT AND type = Story"
# Find .NET related stories
python jira_search.py "project = PLAT AND summary ~ '.NET'"
# Find upgrade/migration tickets
python jira_search.py "project = PLAT AND (summary ~ 'upgrade' OR summary ~ 'migration')"
# Exclude results (use NOT, never use !~ in shell)
python jira_search.py "project = PLAT AND summary ~ 'upgrade' AND NOT summary ~ 'Aspire'"
# Get child stories of an epic
python jira_search.py "parent = PLAT-789"
# Open bugs
python jira_search.py "project = PLAT AND type = Bug AND status != Done"
IMPORTANT: Never use !~ operator directly in shell commands - the ! character triggers bash history expansion and causes escaping errors like \!~.
| Instead of | Use |
|---|---|
summary !~ 'Aspire' | NOT summary ~ 'Aspire' |
status !~ 'Done' | NOT status ~ 'Done' |
labels !~ 'blocked' | NOT labels ~ 'blocked' |
The NOT keyword is JQL-equivalent and shell-safe.
| Script | Purpose |
|---|---|
scripts/jira_fetch.py | Fetch single issue by key |
scripts/jira_search.py | Search issues with JQL |
Output formats: --format markdown (default), --format json, --format table
Credentials from environment variables or .env file:
JIRA_EMAIL=your.email@resolve.io
JIRA_API_TOKEN=your_api_token
Generate token: https://id.atlassian.com/manage-profile/security/api-tokens
The skill detects issue keys matching pattern [A-Z]+-\d+ in conversation:
Detailed information (load as-needed):
| Error | Solution |
|---|---|
| Authentication failed | Check JIRA_EMAIL and JIRA_API_TOKEN |
| Access denied | Verify permissions in Jira web UI |
| Issue not found | Check issue key spelling |
| Invalid JQL | Test query in Jira web UI first |
For detailed troubleshooting: Error Handling Guide
Activates when user mentions:
PLAT-123, JIRA-456When user asks to plan/create a story:
./templates/story-template.mdExample prompt response:
User: "Help me plan a story for adding authentication to actions.api"
Action:
1. Read story template
2. Search for related auth/actions.api issues
3. Draft story using template structure
Version: 2.2.0 Type: Read-Only Scripts: Python 3
This skill's description follows Claude Code skill best practices:
Testing shows descriptions with explicit triggers achieve ~50% auto-activation vs ~20% baseline.