Fix Ticket
Automate the full Jira bug-fix pipeline end-to-end. Use when the user says 'fix ticket', 'fix PROJ-123', 'fix this bug', 'resolve PROJ-XXX', 'fix and ship this ticket', or passes a Jira ticket ID for autonomous bug resolution. Reads the Jira ticket, implements the fix, reviews it, commits, moves the ticket to QA, assigns to QA engineer, and comments with a summary. Also use when the user wants to automate the fix-review-commit-handoff cycle for any Jira bug ticket.
Install
npx skills add EricTechPro/startup-claude-skills --skill fix-ticketgit clone --depth 1 https://github.com/EricTechPro/startup-claude-skills.git /tmp/startup-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/startup-claude-skills/skills/fix-ticket ~/.claude/skills/fix-ticketPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Fix Ticket Automate the full lifecycle of a Jira bug ticket: read the ticket, implement the fix, review changes, commit, transition to QA, assign to QA engineer, and comment with a summary. Zero-touch pipeline from ticket to QA handoff. ## Prerequisites **Read `CONFIG.md` at the start of every run.** This file contains project-specific settings (Jira project key, team members, transition IDs, deployment config, QA credentials). If `CONFIG.md` doesn't exist, warn the user and point them to `CONFIG.template.md`. ## When to Use - User passes a Jira ticket ID (e.g., `PROJ-123`) and wants it fixed end-to-end - User says "fix this ticket", "resolve this bug", "fix and ship PROJ-XXX" - Any bug ticket that needs the full fix-review-commit-handoff cycle ## Parameters | Parameter | Default | Description | |-----------|---------|-------------| | (first arg) | required | Jira ticket ID (e.g., `PROJ-123`) | | `branch` | `ask` | Branch strategy: `ask` (default — prompt user to choose), `worktree` (isolated worktree, auto-merges to main), `main` (commit directly to main), `new` (create fix branch) | | `skip-review` | `false` | Skip the review-team phase | | `skip-jira` | `false` | Skip Jira transition/assign/comment (just fix and commit) | | `assignee` | (from CONFIG.md) | QA assignee: alias from CONFIG.md or a Jira `accountId` | | `auto-commit` | `true` | Auto-commit after fix is verified | | `skip-deploy` | `false` | Skip deployment monitoring |
Details
- Skill name
fix-ticket- Repository
- EricTechPro/startup-claude-skills
- Path
skills/fix-ticket/SKILL.md- License
- MIT
- Repo updated
- 5 June 2026
FAQ
What does the Fix Ticket skill do?
Automate the full Jira bug-fix pipeline end-to-end. Use when the user says 'fix ticket', 'fix PROJ-123', 'fix this bug', 'resolve PROJ-XXX', 'fix and ship this ticket', or passes a Jira ticket ID for autonomous bug resolution. Reads the Jira ticket, implements the fix, reviews it, commits, moves the ticket to QA, assigns to QA engineer, and comments with a summary. Also use when the user wants to automate the fix-review-commit-handoff cycle for any Jira bug ticket.
How do I install the Fix Ticket skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add EricTechPro/startup-claude-skills --skill fix-ticket. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Fix Ticket popular?
It lives in EricTechPro/startup-claude-skills, which has 58 GitHub stars and 18 forks.
Related skills
Develop Team
58EricTechPro/startup-claude-skills
This skill should be used when the user asks to "develop a feature", "implement a ticket", "build PROJ-123", "run the development pipeline", "develop this ticket end to end", or wants fully autonomous feature implementation with parallel research agents, planning, phased implementation, review, and PR creation. Zero checkpoints; pauses only on blockers.
Fix Sentry
58EricTechPro/startup-claude-skills
Scan all unresolved Sentry errors, group by root cause, fix in batch with TDD, and resolve in Sentry after deploy. Use when the user says 'fix sentry errors', 'scan sentry', 'resolve sentry issues', 'fix all errors', 'sentry cleanup', or wants to proactively fix production errors from Sentry monitoring.
Playwright QA CLI
58EricTechPro/startup-claude-skills
Automated QA testing using playwright-cli (CLI tool, NOT MCP tools). Provisions a test user, opens a headless browser, logs in, navigates to target pages, takes screenshots, and generates a REPORT.md. Two modes: VERIFY (reproduce a bug before fixing) and CHECK (confirm a fix works). Use this skill whenever the user says 'QA this', 'test this fix', 'verify this bug', 'smoke test', 'check if this works', 'reproduce this issue', 'run playwright QA', or 'playwright-qa-cli'. Also triggered from /fix-ticket at pre-fix and post-fix stages. Works for any page or user flow — not limited to specific fea
Owasp AI Testing
74mastepanoski/claude-skills
AI trustworthiness testing using OWASP AI Testing Guide v1. Execute 32 test cases across 4 layers (Application, Model, Infrastructure, Data) with practical payloads and remediation.
Stress Test
45gbasin/stress-test-skill
Adversarially stress-test a technical plan by verifying claims against real docs, running POC code, and updating the plan before you build.
Design QA
44sunxin-ai/dsh-design-qa
用 deepseek_vision 看图 —— 判定设计稿与前端实现的保真度、读取图上的具体数值、核对截图内容。当上下文里出现「[图片 …]」这样的文字指针,或需要比对设计稿与实现时使用。
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.