Skip to main content

/

/

Stats

Actions

Tags

Stats

Actions

Tags

ClaudePluginHub

Community directory for discovering and installing Claude Code plugins.

Find plugins for your project

AI-powered recommendations based on your stack.

Product

Browse Plugins
Marketplaces
Pricing
About
Contact

Resources

Learning Center
Blog
Weekly Digest
Claude Code Docs
Plugin Guide
Plugin Reference
Plugin Marketplaces

Community

Browse on GitHub
Get Support

Legal

Terms of Service
Privacy Policy

Browse · Plugins · Top Plugins · Marketplaces · Components · Technologies · Skills · Agents · Commands · Hooks · MCP Servers · LSP Servers · Output Styles · Themes · Monitors

Categories · Productivity · Development · Testing · Deployment · Security · Documentation · Data · Utilities

© 2025 ClaudePluginHub

Community Maintained · Not affiliated with Anthropic

ClaudePluginHub

ClaudePluginHub

Tools Learn Pricing

Search everything...

bughunt-with-jira | bughunt-with-jira

Home
Skills
bughunt-with-jira
bughunt-with-jira

Skill

bughunt-with-jira

From bughunt-with-jira

Systematically hunt and analyze bugs using Jira. Use when the user wants to investigate bugs, triage issues, find related problems, or do root cause analysis using Jira data.

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/bughunt-with-jira:bughunt-with-jira

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

You are a systematic bug hunter. Use the Atlassian MCP tools to search, analyze, and help resolve bugs tracked in Jira.

SKILL.md

34 lines · ~462 tokens

Stats

Parent stars0

MaintenanceGood

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Parent stars0

MaintenanceGood

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

Bug Hunt with Jira

You are a systematic bug hunter. Use the Atlassian MCP tools to search, analyze, and help resolve bugs tracked in Jira.

Workflow

Understand the target: Ask the user what they want to investigate (a specific bug, a component, a pattern of failures, etc.)
Search Jira: Use searchJiraIssuesUsingJql to find relevant issues. Build JQL queries based on the user's description — filter by project, issue type (Bug), status, labels, components, or text.
Analyze issues: For each relevant issue, use getJiraIssue to get full details including description, comments, and linked issues.
Find patterns: Look for:
- Common root causes across related bugs
- Regression patterns (similar bugs reopening)
- Components or areas with high bug density
- Linked issues that reveal systemic problems
Cross-reference code: If the user has a codebase available, search the code for areas mentioned in bug reports to find potential fixes or confirm root causes.
Report findings: Summarize findings with:
- List of relevant issues with key details
- Identified patterns or root causes
- Suggested next steps or fixes
- Priority recommendations

Tips

Start with broad JQL queries, then narrow down based on results
Check issue links (getJiraIssueRemoteIssueLinks, getIssueLinkTypes) for related problems
Look at issue transitions (getTransitionsForJiraIssue) to understand issue lifecycle
Use searchAtlassian for broader searches across Jira and Confluence
When the user provides $ARGUMENTS, use it as the initial search context

$

npx claudepluginhub martin-macak/claude-plugins --plugin bughunt-with-jira

Similar Skills

triage-issue

768

Triages bug reports and error messages by searching Jira for duplicates, checking fix history, and creating structured issues or adding comments.

2 files

View triage-issue

List JIRAs

87

Queries JIRA REST API to fetch raw bug data for projects, including all fields and metadata. Supports filters by component, status, and closed issues for custom analysis.

1 file

View List JIRAs

issue-investigator

11

Investigates Bugs and Incidents on Azure DevOps or Jira by searching chats (Slack/Teams), docs (Confluence), Datadog, and the codebase, then produces an evidence-tagged investigation report.

View issue-investigator