implement-ticket

Automate Jira ticket implementation into a feature branch and GitHub pull request.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the multi-step, error-prone process of taking a Jira ticket from assignment to a merged pull request so non-engineers and engineers alike can ship design system changes reliably without manual git and build steps.

Core Features & Use Cases

  • End-to-end automation: Fetches Jira details, creates a correctly named branch, implements planned file changes, runs builds and type checks, commits with conventional messages, pushes, and opens a PR.
  • Repository and token safety: Enforces branch naming, design token placement in design/GlobalToken.json, build and type verification before pushing, and guidance to follow CONTRIBUTING and CLAUDE conventions.
  • Use case: A designer requests "Implement MPD-74" and receives an implemented feature branch, passing build and type checks, plus a created PR linking the ticket.

Quick Start

Ask the agent to "Implement the Jira ticket MPD-74 end-to-end and create a PR for review".

Frequently Asked Questions about implement-ticket

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

FAQPage Schema
How do I automate creating a pull request from a Jira ticket?

To automate a pull request from a Jira ticket, this Skill fetches ticket details via Atlassian MCP, creates a feature branch, modifies files, runs build and type checks, and opens a GitHub PR end-to-end.

Can I automatically implement design system tokens and component changes from Jira?

Yes, you can implement design system changes from Jira by applying planned modifications to component and token files, specifically enforcing placement within design/GlobalToken.json before running verification checks.

How does branching work when automating Jira ticket implementation for frontend repositories?

Branching for frontend Jira ticket implementation follows a type/description-TICKET naming convention, creating structured feature branches that align with repository standards before pushing changes.

What's the best way to ensure design system branches pass type checks before pushing?

To ensure branches pass type checks before pushing, this Skill automatically executes build and type verification processes locally and enforces token rules, halting the workflow if checks fail.

Do I need Atlassian MCP to turn Jira tickets into merged pull requests?

Yes, you need Atlassian MCP connected to your environment to fetch Jira ticket details automatically, enabling the workflow to read ticket metadata and implement the required file changes seamlessly.

Why does automated Jira ticket implementation enforce conventional commits and token rules?

Automated Jira ticket implementation enforces conventional commits and token rules to maintain repository safety, ensure design system consistency, and comply with CONTRIBUTING and CLAUDE conventions during PR creation.