Code Review & Video Production Skills

Creates agent-ready GitHub issues that are ready to build. Formerly framed as sdd-issue / SDD-ready issue creation. Use when creating a buildable issue, implementation-ready ticket, SDD-ready issue, preparing work for an orchestrator, or when the user says "create an issue", "write a ticket", or "I need to build X". Also use when the user references an existing issue and wants it enriched with scope, constraints, acceptance scenarios, and technical context.

Generate lightweight Product Requirements Documents through a fast, 5-phase guided conversation. Use this skill for MVPs, internal tools, small-to-medium features, or early-stage ideas that need structure but not ceremony. Trigger when the user mentions "PRD light", "light PRD", "quick PRD", "lightweight PRD", "simple PRD", "mini PRD", "short PRD", "brief PRD", "MVP requirements", "MVP spec", "quick requirements", "rough PRD", or asks to "document what we need to build quickly". También se activa en castellano: "PRD ligero", "PRD rápido", "PRD simple", "PRD corto", "mini PRD", "requerimientos ligeros", "requerimientos rápidos", "especificación rápida", "especificación simple", "PRD MVP", "requerimientos del MVP", "documento de requerimientos simple", "PRD breve".

Trigger: prompt review, prompt evaluation, improve prompt, evaluar prompt. Refine prompts for clearer LLM execution.

Comprehensive catalog of 60+ refactoring techniques for Java code based on Martin Fowler's "Refactoring" and Alexander Shvets' "Refactoring Guru". Use this skill whenever the user asks to refactor Java code, improve code quality, eliminate code smells, simplify conditionals, restructure classes, improve API design, or apply any named refactoring technique. Also trigger when the user mentions code smells, legacy code improvement, clean code practices, SOLID principles in Java, or asks "how can I improve this code". Covers Java 8 and Java 11+ examples for every technique. Even if the user just pastes Java code and asks for improvement suggestions, use this skill to identify applicable techniques. También se activa en castellano: "refactorizar", "refactorizar código Java", "mejorar este código", "malos olores del código", "olores de código", "código sucio", "limpiar código", "simplificar condicionales", "principios SOLID", "cómo mejorar este código", "código limpio", "reestructurar clase", "mejorar calidad del código", "técnica de refactorización", "extraer método", "renombrar variable", "mover método", "eliminar código duplicado", "reducir complejidad", "mejorar legibilidad", "reorganizar código".

Implements the TCR (Test && Commit || Revert) methodology for ultra-short, safe commits during refactoring and development. Use this skill whenever the user wants to apply TCR, make atomic commits after each green test, commit frequently during refactoring, or follow a test-driven commit workflow. Also trigger when the user mentions "TCR", "test and commit", "commit after each test", "atomic commits", "micro commits", "revert on red", or asks for a disciplined commit cadence during code changes. También se activa en castellano: "test y commit", "commitear tras cada test", "commits atómicos", "micro commits", "revertir en rojo", "commits pequeños", "flujo TCR", "metodología TCR", "test verde y commit".

Extract, transcribe, and summarize audio or video files using OpenAI Whisper. Use this skill whenever the user wants to transcribe audio or video, extract what was said in a recording, get a transcript of a meeting/interview/lecture/podcast, or generate a summary of spoken content. Also trigger when the user mentions files like .mp3, .mp4, .wav, .m4a, .ogg, .flac, .webm, .mkv, .mov and wants text out of them. Generates a .md file with an AI summary followed by the full literal transcript. También se activa en castellano: "transcribir", "transcripción", "extraer audio", "qué dice este audio", "transcribir reunión", "transcribir entrevista", "pasar audio a texto", "resumir grabación", "transcribir este video", "extraer texto de audio", "transcript", "whisper", "grabar y resumir".

Generate structured Jira acceptance criteria in Gherkin format (Given/When/Then). Use when the user wants to define, write, or create acceptance criteria for a Jira task, story, or ticket. Triggers include "acceptance criteria", "AC", "write the ACs", "define ACs for", or any request to document expected behavior as testable conditions. También se activa en castellano: "criterios de aceptación", "CA", "escribir los criterios", "definir criterios de aceptación", "crear los CA", "ACs del ticket", "criterios Gherkin", "dado cuando entonces", "condiciones de aceptación", "escribir los ACs", "generar criterios", "criterios para esta historia", "definir los criterios".