Menu
Investigate and resolve a Jira issue by reading the ticket, checking blockers, and making code changes
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | resolve |
| description | Investigate and resolve a Jira issue by reading the ticket, checking blockers, and making code changes |
| argument-hint | <PROJ-123> |
Resolve Jira issue with the following steps
jira issue view $ARGUMENTS command.jira issue move $ARGUMENTS "In Progress"
command.rg TICKET from the repo root to search the
ticket in the whole repo. If that's a TODO or FIXME comments, that's a good
pointer for you and you may want to delete or modify them.Marks Jira tickets as Done when their commits have been merged into the current branch. Use whenever the user wants to sync Jira with merged commits — e.g. "mark done", "close tickets from commits", "sync Jira with merged PRs", "any Jira tickets to close?", or after a batch of PRs lands. Works with any Jira project key.
Set up shared Git hooks using gabyx/Githooks (not standard git hooks). Use when a user asks to set up githooks, apply shared hooks, or configure hook repositories in a project.
Generate GitHub Actions CI workflows that call Makefile targets for consistent local and CI behavior. Use when a user asks about CI setup, GitHub Actions, continuous integration, or CI/CD pipelines.
Expert knowledge for Protocol Buffer development. Includes style guidelines, backward compatibility, design patterns, and build system detection (buf, Bazel). Use when creating, modifying, or reviewing .proto files or proto build rules.
Edit JIRA issue descriptions using the jira CLI tool. Use when the user asks to update, modify, or edit a JIRA issue description, or when creating detailed documentation for JIRA tickets.
Create a new Jira bug report with proper wiki markup formatting