new-bug

Create a new Jira bug report with proper wiki markup formatting

Repositorio: jaeyeom/claude-toolbox
Última actividad en el origen: 9 de abril de 2026 a las 22:37
Idioma detectado de SKILL.md: inglés
Estrellas: 1
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/jaeyeom/claude-toolbox --skill new-bug

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

cleanup-worktree-disk

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.

2026-06-26

jira-close-merged

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.

2026-06-26

gabyx-githooks-setup

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.

2026-05-05

Ver todos los de este repositorio

name	new-bug
description	Create a new Jira bug report with proper wiki markup formatting
argument-hint	<PROJECT or EPIC-123>

Report Jira bug with the following steps

First, write the bug report content in a temporary file:
- Use actual newlines, not \n escape sequences and backslash escapes.
- Use Jira wiki markup formatting (see the edit-description skill for detailed formatting rules).
- Jira supports code blocks with {code:language}...{code} syntax
- Common language options: java, go, python, javascript, bash, etc.
Create a bug using jira command:
- If the $ARGUMENTS looks like a project name without number, run the command jira issue create -tBug -s"Summary Text" -b"$(cat description.txt)" -p$ARGUMENTS.
- If the $ARGUMENTS looks like a ticket name with the number, run the command jira issue create -tBug -s"Summary Text" -b"$(cat description.txt)" -P$ARGUMENTS to create a bug under the given Epic.
- Use the email address from jira me to set the assignee: -a"$(jira me --raw | jq -r '.emailAddress')".

new-bug

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio