Search Jira to find and explain internal concepts, processes, and technical details through issues and comments. When Claude needs to: (1) Find or search for information about systems, terminology, processes, deployment, authentication, infrastructure, architecture, or technical concepts, (2) Search issue history, comments, or work logs, (3) Explain what something is, how it works, or look up information, or (4) Synthesize information from multiple Jira sources. Searches in parallel and provides cited answers.
From jiranpx claudepluginhub baleen37/bstack --plugin jiraThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
find information, search jira, look up, what is, explain, issue search, jira search, our documentation, internal knowledge, knowledge base, search for, tell me about, get information about, company systems, terminology, find everything about, what do we know about, deployment, authentication, infrastructure, processes, procedures, how to, how does, our systems, our processes, internal systems, company processes, technical documentation, search issues, find in jira
Search Jira issues, comments, and history to find comprehensive answers to questions about internal concepts, systems, and terminology. This skill performs targeted searches across Jira and synthesizes results with proper citations.
Use this skill when: Users ask about internal company knowledge that might be documented in Jira tickets, comments, or work logs.
Follow this 5-step process to provide comprehensive, well-cited answers:
Extract the core search terms from the user's question.
Examples:
Consider:
Search Jira for relevant information.
Use searchJiraIssuesUsingJql to search Jira issues:
searchJiraIssuesUsingJql(
cloudId="...",
jql="text ~ 'search terms' OR summary ~ 'search terms'"
)
When to use:
Example JQL patterns:
text ~ "Stratus minions"
summary ~ "authentication" AND type = Bug
text ~ "deployment" AND created >= -90d
For most queries, use this sequence:
After identifying relevant sources, fetch full content for comprehensive answers.
When search results reference Jira issues:
getJiraIssue(
cloudId="...",
issueIdOrKey="PROJ-123"
)
Returns: Full issue details including description, comments, status
When to fetch:
Fetch in this order:
Don't fetch everything - be selective based on relevance to user's question.
Combine information from multiple sources into a coherent answer.
Structure your answer:
Direct Answer First
Detailed Explanation
Source Attribution
Highlight Discrepancies
Provide Context
Pattern 1: Multiple sources agree
Stratus minions are background worker processes that handle async tasks.
According to several Jira tickets (PROJ-145, PROJ-203) which discuss
minion configuration and scaling strategies.
Pattern 2: Sources provide different aspects
The billing system has two main components:
**Payment Processing** (from PROJ-189)
- Handles credit card transactions
- Integrates with Stripe API
- Runs nightly reconciliation
**Invoice Generation** (from PROJ-200)
- Creates monthly invoices
- Note: Currently has a bug where tax calculation fails for EU customers
- Fix planned for Q1
Pattern 3: Conflicting information
There is conflicting information about the authentication timeout:
- **Official Decision** (PROJ-456, Oct 2023): 30-minute session timeout
- **Implementation Reality** (PROJ-789, filed Dec 2023): Actual timeout is
15 minutes due to load balancer configuration
- **Status:** Engineering team aware, fix planned but no timeline yet
Current behavior: Expect 15-minute timeout.
Pattern 4: Incomplete information
Based on available Jira issues:
[What we know about deployment process from issues]
However, I couldn't find information about:
- Rollback procedures
- Database migration handling
You may want to check with the DevOps team or search for additional documentation.
Always include links to source materials so users can explore further.
For Jira issues:
**Related Tickets:**
- [PROJ-123](https://yoursite.atlassian.net/browse/PROJ-123) - Brief description
- [PROJ-456](https://yoursite.atlassian.net/browse/PROJ-456) - Brief description
Complete citation section:
## Sources
**Jira Issues:**
- [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion scaling implementation
- [PROJ-203](https://yoursite.atlassian.net/browse/PROJ-203) - Performance optimization
Do:
Don't:
Good results:
Questionable results:
When results are poor:
If searches return no results:
I searched Jira but couldn't find information about "[topic]".
This could mean:
- The concept hasn't been documented in Jira yet
- It might be called something else (can you provide alternative names?)
- Documentation might be in a different system
Would you like me to:
1. Try searching with different terms?
2. Search for related concepts?
3. Look for mentions in recent Jira tickets?
If search returns 50+ results:
If the user's question is vague:
I found information about several topics related to "[term]":
1. [Topic A] - from PROJ-123
2. [Topic B] - from PROJ-456
3. [Topic C] - from PROJ-789
Which aspect are you most interested in?
If you find information is old:
I found information about [topic], but note that it's from [date] and may be outdated.
[Provide the information anyway]
You may want to verify this is still current, especially if it's from more than
a year ago.
User: "What are Stratus minions?"
Process:
searchJiraIssuesUsingJql(cloudId="...", jql='text ~ "Stratus minions"')Answer:
Stratus minions are background worker processes that handle asynchronous task
processing in the Stratus system.
**Key Characteristics:**
- Run independently from web servers
- Process jobs from a Redis queue
- Can be scaled horizontally for increased throughput
- Handle tasks like email sending, report generation, and data processing
**Architecture:**
According to PROJ-145, minions follow a worker-queue pattern where:
1. Web application enqueues tasks
2. Minions poll the queue for work
3. Tasks are processed asynchronously
4. Results are stored in the database
**Implementation Notes:**
From PROJ-203, the current deployment runs 5 minion instances,
with plans to scale to 10 for handling increased load.
## Sources
- [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion architecture design
- [PROJ-203](https://yoursite.atlassian.net/browse/PROJ-203) - Minion scaling implementation
User: "How long is our session timeout?"
Process:
Answer:
There is a discrepancy between documented and actual behavior:
**Official Decision** (PROJ-456):
Session timeout is configured for 30 minutes of inactivity.
**Actual Behavior** (PROJ-789, reported Dec 2023):
Users are being logged out after 15 minutes due to a load balancer configuration
that overrides the application setting.
**Current Status:**
The engineering team is aware of this issue. The load balancer timeout needs to
be adjusted to match the application setting. No fix timeline has been set.
**Recommendation:** Plan for 15-minute timeout until this is resolved.
## Sources
- [PROJ-456](https://yoursite.atlassian.net/browse/PROJ-456) - Original timeout decision
- [PROJ-789](https://yoursite.atlassian.net/browse/PROJ-789) - Timeout discrepancy bug report
User: "Explain our deployment process"
Process:
Answer:
Based on available Jira issues, here's what I found about the deployment process:
**Build Phase** (from PROJ-789):
1. Code pushed to main branch triggers CI pipeline
2. Automated tests run (unit, integration)
3. Docker image built and pushed to registry
**Deployment Phase** (from PROJ-790):
4. Staging deployment happens automatically
5. Manual approval required for production
6. Blue-green deployment strategy used
**Gaps in Documentation:**
I couldn't find documented information about:
- Rollback procedures
- Database migration handling
- Post-deployment verification steps
These details may exist in tribal knowledge or need to be documented.
## Sources
- [PROJ-789](https://yoursite.atlassian.net/browse/PROJ-789) - CI/CD pipeline setup
- [PROJ-790](https://yoursite.atlassian.net/browse/PROJ-790) - Deployment pipeline implementation
Would you like me to search for more specific aspects of deployment?
This skill is for Jira-based knowledge search only. Do NOT use for:
Examples of what NOT to use this skill for:
Primary tool: searchJiraIssuesUsingJql(cloudId, jql) - Search Jira issues
Follow-up tools:
getJiraIssue(cloudId, issueIdOrKey) - Get full issue detailsAnswer structure:
Remember: