Menú
Read this skill before making git commits
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
Work on a Linear issue by ID. Fetch issue details, classify it as a bug, task, or unclear request, gather the right context, create the Linear branch from latest master, implement simple changes, and verify with tests, lint, and typecheck. Bugs require root cause analysis and production evidence when useful. Tasks require clarified requirements, acceptance criteria, constraints, and tradeoffs.
Sync changes made to live dotfiles back into the chezmoi source repo. Use when the user has edited a file in their home directory (or other chezmoi target) and wants the chezmoi source (plain files, `.tmpl` templates, or included partials under `.chezmoitemplates/`) updated so `chezmoi diff` is clean again. Triggers on: "sync to chezmoi", "pull changes into chezmoi", "update the template to match", "make chezmoi diff empty".
DNS and domain information lookup. Use for checking DNS records (A, AAAA, MX, TXT, NS, CNAME, SOA), WHOIS data, and domain availability. Helps with domain research, troubleshooting DNS issues, and finding if a domain is registered or free.
Interpret, explain, write, and update Finicky v4 configuration for macOS URL routing. Use when working with ~/.finicky.js or ~/.finicky.ts, reading an existing Finicky setup, authoring rewrite or handler rules, choosing browsers or profiles, debugging rule order, or migrating routing logic into Finicky.
Manage stacked Git branches with git-spice. Use when the user wants to create, navigate, restack, or submit stacked branches and Change Requests (PRs/MRs). Triggers on: stacking branches, git-spice commands, submitting stacked PRs, restacking, navigating branch stacks, syncing with trunk.
Produce natural, engaging, well-structured writing based strictly on user-provided pointers. The output must feel authored by a thoughtful human with opinions and lived experience. Use this skill when the user asks to write or edit text based on their ideas, notes, or bullet points. The writing should avoid generic AI-style phrasing and instead feel like it was crafted by a real person with a unique voice.
| name | commit |
| description | Read this skill before making git commits |
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).