jira-assistant-skills

Browse all available JIRA skills with descriptions and examples

Set up JIRA Assistant Skills with credentials and configuration

Discover JIRA project context for intelligent defaults and workflow understanding

Get detailed information about a specific JIRA skill

**Skill File:** `/Users/jasonkrueger/IdeaProjects/Jira-Assistant-Skills/skills/jira-time/SKILL.md`

Reviews jira-admin SKILL.md documentation against jira-as admin CLI. Use when validating documentation accuracy or after CLI updates.

This directory contains detailed findings from systematic reviews of JIRA Assistant Skills documentation against actual CLI implementations.

**Date:** 2026-01-31

**Date:** 2026-01-31

**Reviewed:** 2026-01-31

Reviews jira-agile SKILL.md documentation against jira-as agile CLI. Use when validating documentation accuracy or after CLI updates.

Reviews jira-assistant hub SKILL.md routing logic and skill references. Use when validating hub documentation or after adding new skills.

Reviews jira-bulk SKILL.md documentation against jira-as bulk CLI. Use when validating documentation accuracy or after CLI updates.

Reviews jira-collaborate SKILL.md documentation against jira-as collaborate CLI. Use when validating documentation accuracy or after CLI updates.

Reviews jira-dev SKILL.md documentation against jira-as dev CLI. Use when validating documentation accuracy or after CLI updates.

Reviews jira-fields SKILL.md documentation against jira-as fields CLI. Use when validating documentation accuracy or after CLI updates.

Reviews jira-issue SKILL.md documentation against jira-as issue CLI. Use when validating documentation accuracy or after CLI updates.

Reviews jira-jsm SKILL.md documentation against jira-as jsm CLI. Use when validating documentation accuracy or after CLI updates.

Reviews jira-lifecycle SKILL.md documentation against jira-as lifecycle CLI. Use when validating documentation accuracy or after CLI updates.

Reviews jira-ops SKILL.md documentation against jira-as ops CLI. Use when validating documentation accuracy or after CLI updates.

Reviews jira-relationships SKILL.md documentation against jira-as relationships CLI. Use when validating documentation accuracy or after CLI updates.

Reviews jira-search SKILL.md documentation against jira-as search CLI. Use when validating documentation accuracy or after CLI updates.

Reviews jira-time SKILL.md documentation against jira-as time CLI. Use when validating documentation accuracy or after CLI updates.

Orchestrates parallel documentation reviews across all jira-* skills. Aggregates findings into unified report. Use when running full audit.

Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.

Epic creation and sprint management - create epics, manage sprints, view backlog, estimate with story points. TRIGGERS: 'create an epic', 'create epic', 'new epic', 'show the backlog', 'view backlog', 'add to sprint', 'move to sprint', 'set story points', 'sprint planning', 'epic for', 'link to epic', 'sprint list', 'active sprint', 'velocity', 'create subtask'. NOT FOR: bugs/tasks/stories without epic context (use jira-issue), field ID discovery (use jira-fields), searching issues by JQL (use jira-search), transitioning issues through workflow (use jira-lifecycle).

JIRA automation hub routing to 13 specialized skills for any JIRA task: issues, workflows, agile, search, time tracking, service management, and more.

Bulk operations for multiple issues at scale. TRIGGERS: 'bulk update', 'bulk close', 'bulk transition', 'bulk assign', 'transition N issues' (N >= 10), 'update all bugs', 'close 50 issues', 'mass transition', 'update multiple issues', quantities like '50 issues', '100 bugs', '20+ tickets'. Use for operations on 10+ issues. NOT FOR: single issue transitions (use jira-lifecycle), searching only without modifications (use jira-search), single issue field updates (use jira-issue).

Collaborate on issues: add/edit comments, share attachments, notify users, track activity. For team communication and coordination on JIRA issues.

Git and developer workflow integration. TRIGGERS: 'generate branch name', 'create branch name', 'branch name for', 'write PR description', 'PR description for', 'link PR', 'link pull request', 'parse commit', 'extract issue from commit', 'smart commit', 'development panel'. Use for Git, GitHub, GitLab, Bitbucket integration with JIRA. NOT FOR: issue field updates (use jira-issue), searching issues (use jira-search), status transitions (use jira-lifecycle).

Custom field discovery and configuration. TRIGGERS: 'field ID for', 'what's the field ID', 'what is the field ID', 'list custom fields', 'what fields are available', 'what custom fields', 'show custom fields', 'customfield_', 'find field', 'agile fields', 'configure agile fields', 'story points field'. Use for JIRA field metadata and discovery. NOT FOR: setting field values on issues (use jira-issue), setting story points (use jira-agile), searching by field values (use jira-search).

Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile), transitions/status changes (use jira-lifecycle), comments/attachments (use jira-collaborate), time tracking (use jira-time), bulk operations on 10+ issues (use jira-bulk), dependencies/blockers (use jira-relationships), branch names/PR descriptions (use jira-dev).

Complete ITSM/ITIL workflow support for JSM - service desks, requests, SLAs, customers, approvals, knowledge base. Use when managing service desk requests, tracking SLAs, or handling customer operations.

Manage issue lifecycle through workflow transitions and status changes. Control who does what and when via assignments, versions, and components.

JIRA cache and performance operations. TRIGGERS: 'warm the cache', 'warm cache', 'cache status', 'clear cache', 'cache warm', 'cache for project', 'discover project', 'project discovery', 'cache hit rate', 'optimize performance', 'rate limit'. Use for JIRA API performance optimization and project context discovery. NOT FOR: project configuration/settings (use jira-admin), issue operations (use jira-issue), bulk issue modifications (use jira-bulk).

Issue linking, blockers, and dependency analysis. TRIGGERS: 'what's blocking', 'what is blocking', 'is blocked by', 'link issues', 'link to', 'blockers for', 'depends on', 'clone issue', 'clone with', 'blocking chain', 'dependency graph', 'show dependencies', 'get blockers', 'relates to', 'duplicates'. Use for issue dependencies, relationships, and cloning. NOT FOR: epic linking (use jira-agile), field updates (use jira-issue), bulk cloning (use jira-bulk).

Find issues by criteria (status, assignee, priority, etc.) using JQL. Create filters, export results to CSV/JSON, bulk update. Ideal for reporting and automation.

Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations on issues. NOT FOR: SLA tracking (use jira-jsm), date-based issue searches (use jira-search), issue field updates unrelated to time (use jira-issue).