Loading...
Loading...
Found 163 Skills
A comprehensive Git assistant skill that provides intelligent branch management, commit message conventions, workflow assistance, and code review guidance. Automatically activates when users perform Git operations or use /git commands.
Use when writing git commit messages for non-trivial changes — captures decision context (constraints, rejected alternatives, confidence, directives) as structured git trailers so future agents and developers can query project knowledge via git log --trailer=
Create git commits using conventional commits with scopes. Use when the user asks to commit, make a commit, save changes, or any git commit operation. Never include Co-Authored-By lines, AI agent mentions, or any reference to Claude, AI, or automated tooling in commit messages.
Set up and configure Git pre-commit hooks for code quality, secrets scanning, and commit message validation. Use when installing git hooks, configuring pre-commit checks, or enforcing code standards.
Create a git commit following the Conventional Commits specification.
Utiliza esta habilidad para analizar cambios locales en el repositorio Git, redactar mensajes de commit profesionales en español y ejecutar commit/push de forma segura.
Generate branch name, commit message, and PR content from one shared diff context
Generates conventional one line commit messages from a git diff
Git Workflow Standard Operating Procedures, including commit message generation and remote repository synchronization
Stages files, analyzes the diff, and commits with a conventional commit message. Use this skill whenever the user wants to commit, says things like "commit this", "make a commit" or "ship it".
Fetch upstream, rebase, stage all changes, run ADR compliance check on modified artifacts, generate a descriptive commit message from the diff, commit, and push to the current branch's upstream. Handles merge conflicts by preferring local changes for config/project files and upstream for scaffolding.
Create git commits in Conventional Commits format. Estimate type/scope from staged changes, detect breaking changes and secret leaks (such as .env files). Must pass pre-commit hooks (`--no-verify` is not allowed). Use with instructions like "commit", "git commit", "record changes".