Menú
Generate commit messages for staged git changes. Use when the user asks to generate a commit message or wants help writing commit messages.
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.
Basado en la clasificación ocupacional SOC
Debug errors using logs and stack traces. Use when the user shares an error message, crash log, or runtime issue to fix.
Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?"
Explain errors without editing files. Use when the user wants to understand an error or crash but not immediately fix it.
Analyze code for logical errors, runtime bugs, and edge cases. Use when the user wants a code review, asks to find bugs, or wants to check code correctness.
Image manipulation via a bundled script, resizing, rotation, flipping, cropping, padding, format conversion (JPEG/PNG/WebP/TIFF/HEIC), transparency operations (remove/replace/extract/blend), grayscale conversion, auto-cropping borders, and file size optimization.
Convert documents to Markdown. PDFs go through the LlamaParse API (best quality, costs credits, tier selectable) or a local PyMuPDF engine (free, offline, no API key); other formats (DOCX, PPTX, XLSX, HTML, EPUB) are converted locally with markitdown.
| name | commit-message |
| description | Generate commit messages for staged git changes. Use when the user asks to generate a commit message or wants help writing commit messages. |
When generating commit messages, follow every step in order:
Check for staged changes: Run git diff --cached --stat. If nothing is staged, stop and tell the user to stage changes first with git add. Do not invent a message.
Match the repo's convention: Run git log --oneline -10. If recent messages use a prefix convention (feat:, fix:, chore:), use the same convention. If not, use plain sentences.
Review the changes: Run git diff --cached. Base the message ONLY on what this diff actually contains, never on what the user says they intended but did not stage.
Choose the format:
Apply the style rules: present tense, active voice ("Add X", not "Added X" or "Adds X"), specific ("Fix null check in login handler", not "Fix bug").
Output: present the message in a fenced code block and nothing else after it. Do not run git commit unless the user explicitly asks.
Examples
Single-line:
feat: add JWT validation to login endpoint
Multi-line:
refactor: overhaul user authentication
- add JWT validation middleware
- update login and signup endpoints
- hash passwords with bcrypt
Guardrails: never mention files that are not in the staged diff; never exceed 50 characters on the summary line; never use passive voice; never add a body when one bullet would restate the summary.