Menú
Use when creating git commits -- determines type, scope, and message from staged changes
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
Use when reviewing a spec or task graph for completeness before implementation
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when decomposing a spec, design, or feature description into a task dependency graph with self-evaluating acceptance criteria
Use when doing creative product, feature, component, functionality, or behavior design work
Use when infrastructure or features are built but before declaring done -- verifies work is wired into the system and actively used
| name | git-commits |
| description | Use when creating git commits -- determines type, scope, and message from staged changes |
<type>(<scope>): <imperative description>
Imperative mood: "add feature" not "added feature" or "adds feature".
| Type | When | Tier |
|---|---|---|
feat | New functionality, new files with exports | 1 — full context |
fix | Bug fix, error handling correction | 1 — full context |
refactor | Restructure without behavior change | 2 — brief context |
test | Add/update tests only | 2 — brief context |
docs | Documentation, comments | 3 — summary only |
chore | Dependencies, config, tooling | 3 — summary only |
perf | Performance improvement | 1 — full context |
ci | CI/CD pipeline changes | 3 — summary only |
build | Build system, packaging | 3 — summary only |
style | Formatting, linting (no logic change) | 3 — summary only |
Infer from the primary area of change:
internal/auth/token.go → authcmd/oro/ → oro.Codex/skills/ → skillsfeat: add retry logic across servicesTier 1 (feat, fix, perf): Body with what changed and why. List affected files if 3+.
Tier 2 (refactor, test, build, ci): One-line body if helpful. Skip if obvious.
Tier 3 (docs, style, chore): Subject line only. No body needed.
feat(auth): add token refresh not feat: add auth token refresh# Tier 1 — full context
git commit -m "feat(skills): add 4 skills from openclaw and tasks"
# Tier 1 — with body
git commit -m "$(cat <<'EOF'
fix(sync): resolve race condition in concurrent token refresh
Token store was not mutex-protected during refresh. Multiple goroutines
could trigger simultaneous refreshes, causing token overwrites.
EOF
)"
# Tier 2
git commit -m "refactor(storage): extract query builder from sqlite module"
# Tier 3
git commit -m "docs: update cross-reference notes"
git commit -m "chore: bump golangci-lint to v1.62"
git diff --staged