jira-ticket-start

Fetch Jira ticket details, create a feature branch, and assess codebase complexity.

7|Updated Dec 5, 2023
One-click install
npx skills add https://github.com/mParticle/aquarium --skill jira-ticket-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-ticket-start
Source: https://github.com/mParticle/aquarium/tree/main/.claude/skills/jira-ticket-start
Command: npx skills add https://github.com/mParticle/aquarium --skill jira-ticket-start

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Developers waste time onboarding Jira tickets: hunting for ticket context, creating correctly named branches, and starting a focused codebase investigation. This Skill centralizes ticket details, enforces branch naming conventions, and produces an initial investigation and complexity assessment so engineers can begin implementation with full context.

Core Features & Use Cases

  • Fetch ticket details from Atlassian MCP including summary, description, acceptance criteria, status, and priority.
  • Create feature branches that follow repository conventions and ensure work happens on the correct base (pull main first).
  • Kick off investigation by locating related files, identifying integration points, and estimating LOC-based complexity (Simple/Medium/Complex).
  • Transition ticket status to In Progress when appropriate and produce an actionable output: ticket summary, branch name, investigation findings, and recommended next steps.
  • Use case: A developer picks up PROJ-123 and uses the Skill to fetch details, create feat/add-tooltip-PROJ-123, surface related components, and determine if a multi-step plan is needed.

Quick Start

Start work on PROJ-123 by running the jira-ticket-start skill with the ticket ID to fetch details, create the correctly named branch, and produce an investigation summary.

Frequently Asked Questions about jira-ticket-start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start working on a Jira ticket and create the correct feature branch?

Starting a Jira ticket involves fetching issue details via Atlassian MCP, pulling the latest main branch, and creating a convention-compliant feature branch. This initiates codebase investigation by locating related files and integration points to provide full context.

What is the best way to onboard a new Jira backlog item into development?

Onboarding a Jira backlog item is best handled by fetching ticket context, creating a naming-compliant branch, and running an initial codebase investigation. This centralizes summary details and produces a complexity assessment so engineers can begin implementation immediately.

Does Jira ticket branching workflow support TypeScript React component libraries?

Yes, the Jira ticket branching workflow explicitly supports developers working on a TypeScript React component library. It locates related components and integration points to estimate code complexity for this specific technical stack.

Can I transition Jira issue status to In Progress automatically when creating a branch?

Yes, you can transition Jira issue status to In Progress when starting a new ticket. The workflow uses Atlassian MCP API calls to retrieve issues and transition ticket status automatically as part of the branch creation output.

How does codebase investigation estimate complexity for a new Jira issue?

Codebase investigation estimates complexity by locating related files, identifying integration points, and measuring LOC-based metrics. It categorizes the Jira issue as Simple, Medium, or Complex to determine if a multi-step implementation plan is needed.