Agent skill
start-ticket
Initialize work on a Jira ticket. Creates a new branch with conventional commit prefix based on the ticket type. Use when starting work on a new ticket.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/start-ticket
SKILL.md
Start Ticket
Initialize work on a Jira ticket by looking up the ticket details and creating an appropriately named branch.
Usage
/start-ticket AB-123
Instructions
1. Look Up the Jira Ticket
Use the /jira-ticket skill or the Jira MCP tools directly to fetch the ticket details:
mcp__jira__jira_get with:
path: /rest/api/3/issue/{ticketNumber}
jq: "{key: key, summary: fields.summary, type: fields.issuetype.name}"
2. Determine the Branch Prefix
Map the Jira issue type to a conventional commit prefix:
| Issue Type | Branch Prefix |
|---|---|
| Story | feat |
| Task | feat |
| Bug | fix |
| Spike | chore |
| Sub-task | inherit from parent, or feat |
| Improvement | feat |
| Technical Debt | refactor |
| Documentation | docs |
| Default | feat |
3. Generate Branch Name
Format: {prefix}/{TICKET-NUMBER}-{kebab-case-summary}
Rules:
- Convert summary to kebab-case (lowercase, hyphens instead of spaces)
- Remove special characters except hyphens
- Truncate to reasonable length (max ~50 chars for the summary portion)
- Keep the ticket number uppercase
Example: For ticket AB-123 with summary "Sanitize Input":
feat/AB-123-sanitize-input
4. Create the Branch
# Ensure we're on main and up to date
git checkout main
git pull origin main
# Create and switch to new branch
git checkout -b {branch-name}
5. Confirm to User
Output the created branch name and ticket summary so the user knows they're ready to start work.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?