From pr-to-ticket
File Linear tickets from PR review feedback and notify the PR author. Use when asked to file a ticket from PR comments, create a ticket from PR feedback, ticket PR concerns, or create a Linear ticket from a PR review. Triggers on phrases like "file ticket from PR", "ticket the PR concerns", "linear ticket for PR", "create ticket from PR feedback", or "ticket this review".
How this skill is triggered — by the user, by Claude, or both
Slash command
/pr-to-ticket:pr-to-ticketThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
File Linear tickets from PR review feedback and notify the PR author.
File Linear tickets from PR review feedback and notify the PR author.
This skill automates the workflow of:
Get the current PR info:
gh pr view --json number,headRepository,author
gh repo view --json nameWithOwner
Retrieve all comment sources:
# PR-level comments
gh api /repos/{owner}/{repo}/issues/{number}/comments
# Review comments (inline on code)
gh api /repos/{owner}/{repo}/pulls/{number}/comments
# Reviews with body text
gh api /repos/{owner}/{repo}/pulls/{number}/reviews
Skip these:
<!-- linear-linkback -->, CI bots)Identify actionable items:
Extract from comments:
 or <img ...>)Detect parent ticket:
Present a summary of detected concerns using AskUserQuestion:
Use mcp__linear__create_issue with:
Title: Concise description of the concern(s)
Team: Based on concern type heuristics (see below)
Description template:
## Context
Follow-up from PR #{number} ({pr_title}). {brief_context}
## Concerns to Address
### 1. {Concern Title}
{Concern description from review}
{Include any screenshots}
### 2. {Additional concerns if multiple}
...
## Next Steps
- {Suggested action items}
## Related
- PR: {pr_url}
- Parent ticket: {parent_ticket_id if detected}
Links: Attach the PR URL using the links parameter
Notify the PR author:
gh pr comment {number} --body "@{pr_author} Filed ticket for the feedback: {linear_ticket_url}"
Tell the user what was created:
Created Linear ticket {TEAM-123}: {title}
URL: {linear_url}
Tagged @{author} in PR #{number}
| Concern Type | Keywords | Suggested Team |
|---|---|---|
| UI/Visual | "visual", "design", "UI", "looks", "styling", "doesn't look right" | Design |
| UX | "confusing", "UX", "user experience", "hard to use" | Design |
| Bug | "bug", "broken", "doesn't work", "error", ":bug:" | Development |
| Performance | "slow", "performance", "optimize", "laggy" | Development |
| Tech Debt | "refactor", "cleanup", "tech debt" | Development |
| Default | (anything else) | Development |
npx claudepluginhub franchiseai/claude-code-plugins --plugin pr-to-ticketTriages unresolved GitHub PR review threads via webform, summarizes reviewer feedback, and dispatches fixes through whip-start. Use after receiving PR reviews.
Creates well-written tickets for your team's tracker (Linear, GitHub, Jira) by interviewing the user and routing to the appropriate pack.
Interactively responds to PR review feedback: fetches comments, verifies findings, asks for user approval, makes changes, and posts replies. Use when addressing GitHub pull request reviews.