Automated summary
Fetches complete details of a Jira ticket (summary, description, status, priority, assignee, etc.) to understand task context.
Strengths
- Provides a structured overview of the ticket (status, priority, type) in a single command.
- Includes creation and update dates along with linked issues for broader context.
- Integrates into a ticket-driven development workflow, making it easy to load context before implementing.
- Supports multiple output formats (text, JSON, markdown) for flexibility.
Limitations
- Requires the 'aide' tool to be installed and configured with proper Jira access.
- Does not handle comments or discussion history (a separate 'ticket-comments' skill is needed for that).
- Depends on the Jira API; may fail if the ticket is inaccessible or permissions are insufficient.
Use this skill when you need to view the details of a Jira ticket before starting a task, to understand requirements or check status.
Do not use it to modify a ticket, comment, or change its status – other skills are dedicated to those actions.
Security analysis
SafeThe skill only instructs running a read-only 'aide jira view' command, with no destructive operations, no data exfiltration, and no obfuscation. It uses Bash(aide:*) but only for a specific safe command.
No concerns found
How this analysis is madeExamples
Show me the full details of Jira ticket PROJ-123, including status, priority, and assignee.What is the ticket TASK-456 about? I need to understand the requirements before I start working on it.Load the Jira ticket for our current sprint issue so I can review the acceptance criteria.name: ticket description: View Jira ticket details to understand requirements and context. Use when the user mentions a ticket key, wants to understand a task, needs to load ticket context, or starts work on an issue. allowed-tools: Bash(aide:*)
View Jira Ticket
Fetch detailed information about a Jira ticket to understand requirements and context.
When to Use
- User mentions a ticket key (e.g., "PROJ-123")
- User wants to understand a task's requirements
- User asks "what's this ticket about?"
- User is starting work on an issue
How to Execute
Run:
aide jira view <TICKET-KEY> [--format text|json|markdown]
Output Includes
- Summary and description
- Status, priority, type
- Assignee and reporter
- Labels and components
- Created and updated dates
- Any linked issues
Ticket-Driven Development Workflow
Starting Work on a Ticket
- Load ticket context: Use this skill to fetch full details
- Understand requirements: Review description and acceptance criteria
- Check for blockers: Look for linked issues or dependencies
- Review comments: Use ticket-comments skill for discussion history
During Development
- Reference ticket requirements while coding
- Track progress with comments using ticket-comment skill
- Update description if scope changes using ticket-update skill
- Stay aligned by checking for new comments
Completing Work
- Add summary comment documenting what was implemented
- Reference in commits (e.g., "PROJ-123: Add feature")
- Link PR in closing comment
- Transition status using ticket-transition skill
Best Practices
- Always load ticket context before starting implementation
- Keep the ticket updated as you progress
- Use ticket key in commit messages for traceability
- Check comments for clarifications from stakeholders
Next Steps
After loading ticket:
- Use ticket-comments skill to see discussion history
- Use ticket-update skill to modify fields
- Use ticket-transition skill to change status
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/view-jira-ticket-details-mmio70s1/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/view-jira-ticket-details-mmio70s1' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/view-jira-ticket-details-mmio70s1/download' --output '.skill-downloads/view-jira-ticket-details-mmio70s1/SKILL.md.part' && mv '.skill-downloads/view-jira-ticket-details-mmio70s1/SKILL.md.part' '.skill-downloads/view-jira-ticket-details-mmio70s1/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash(aide:*)
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/view-jira-ticket-details-mmio70s1/SKILL.md' && test -s '.skill-downloads/view-jira-ticket-details-mmio70s1/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ticket' && cp -R '.skill-downloads/view-jira-ticket-details-mmio70s1' '.claude/skills/ticket'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/view-jira-ticket-details-mmio70s1'openskills read 'view-jira-ticket-details-mmio70s1'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/view-jira-ticket-details-mmio70s1/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.