jira-ticket
Look up Jira ticket details including summary, type, and description. Use this to fetch ticket context for branch naming, PR creation, or understanding requirements.
Browse published AI skills maintained by flurdy. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
10Repository stars across indexed skills
10Repository forks
0Average repository stars per indexed skill
1Repository stars may repeat across skills from the same repository.
Look up Jira ticket details including summary, type, and description. Use this to fetch ticket context for branch naming, PR creation, or understanding requirements.
Address PR review comments from reviewers (amazon-q-developer, copilot, humans). Use when the user wants to see and respond to feedback on their pull request.
Create bead(s) from a user prompt. Investigates relevance, checks for duplicates, and may split complex requests into multiple focused beads. Use when given a feature request, bug report, or task description th...
Pick the next bead to work on. Shows ready tasks (no blockers), applies user preferences for ordering (priority, type, recency), and helps select work.
Rebase after a parent PR has been merged to main. Use when your branch was stacked on another PR that has now been merged, and you need to rebase onto main while keeping only your commits.
Rebase the current branch onto an updated main branch. Use when main has been updated and you need to incorporate those changes into your feature branch.
Create a new branch stacked on another PR. Use when you want to start work that depends on an existing PR that hasn't been merged yet.
Create a pull request from the current branch following project conventions. Uses the branch name to find the Jira ticket, generates a PR with the standard template, and pushes to origin.
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.
Rebase the current branch onto an updated parent PR branch. Use when you have stacked PRs and the parent branch has been updated (force-pushed after its own rebase or new commits added).
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.