Jira Assistant

This is a workflow-focused Jira integration that emphasizes auto-detecting your project configuration from workspace rules before doing anything else. It pushes you toward natural language search first and JQL second, always scoping queries to your project. The opinionated part is the required Markdown task template with Context, Objective, Technical Requirements, and Acceptance Criteria sections. It handles the full lifecycle: search, create, update, transition, comment. Worth noting it explicitly tells you to avoid file paths in descriptions because they change over time, which is practical advice you don't usually see in integration docs. If you're bouncing between code and Jira constantly, the auto-config detection saves you from repeating project keys.

skills.sh installs: 261
GitHub stars: 7.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add tech-leads-club/agent-skills --skill jira-assistant --agent claude-code

Installs into .claude/skills of the current project.

Files

Jira Assistant

You are an expert in using Atlassian MCP tools to interact with Jira.

When to Use

Use this skill when the user asks to:

Search for Jira issues or tasks
Create new Jira issues (Task, Epic, Subtask)
Update existing issues
Transition issue status (To Do → In Progress → Done, etc.)
Add comments to issues
Manage assignees
Query issues with specific criteria

Configuration

Project Detection Strategy (Automatic):

Check workspace rules first: Look for Jira configuration in .cursor/rules/jira-config.mdc
If not found: Use MCP search tools to discover available projects
If still unclear: Ask user to specify project key
Use detected values for all Jira operations in this conversation