Menú
Create git commits using Conventional Commits format
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
Query and modify databases (PostgreSQL, MySQL/MariaDB, SQLite). Use when the user asks to inspect, query, or write to a database, or when you need to understand a database schema.
Use when asked to find a project, work on a project, start a feature, fix a bug, or make changes to a repo.
Retrieve up-to-date documentation for libraries and frameworks via the Context7 API. Use when looking up docs for any library, finding code examples, verifying API usage, or getting current info that may have changed since training.
Deep codebase analysis with extended thinking — use for complex tasks that may lead to implementation
Update the changelog for a new release
Interact with local Chrome browser session (only on explicit user approval after being asked to inspect, debug, or interact with a page open in Chrome)
| name | commit |
| description | Create git commits using Conventional Commits format |
Create a git commit for the current changes using a concise Conventional Commits-style subject.
<type>(<scope>): <summary>
type REQUIRED. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.Signed-off-by).git status and git diff to understand the current changes (limit to argument-specified files if provided).git log -n 50 --pretty=format:%s to see commonly used scopes.git commit -m "<subject>" (and -m "<body>" if needed).