Menu
Update a Jira ticket description after investigating the codebase
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
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.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/jaeyeom/claude-toolbox --skill updateThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Reclaim macOS disk space by removing git worktrees whose PRs are already merged (plus their branches and Bazel output bases) and by deleting orphaned Bazel output bases whose workspace directory no longer exists. Use whenever the user is low on disk, says "clean up disk space", "free up space", "my disk is full", "clean up worktrees", "remove merged worktrees", "the bazel cache is huge", or after a batch of PRs has merged and stale worktrees pile up. Bazel output bases dominate disk (often 9–12 GB each), so reach for this even when the user only mentions worktrees — the cache is usually the real win.
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.
Showing SKILL.md
Based on SOC occupation classification
| name | update |
| description | Update a Jira ticket description after investigating the codebase |
| argument-hint | <PROJ-123> |
Update Jira ticket with the following steps
jira issue view $ARGUMENTS command.\n escape sequences and backslash escapes.edit-description skill for
detailed formatting rules).{code:language}...{code} syntaxjira issue edit $ARGUMENTS -s"Summary Text" -b"$(cat description.txt)" --no-input