Menu
Treat commits as save points, branches as isolated environments, and history as a record of decisions.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | git-workflow-and-versioning |
| description | Treat commits as save points, branches as isolated environments, and history as a record of decisions. |
| when-to-use | Before committing, branching, or reviewing git history. |
Git is your safety mechanism. Commits are save points. Branches are isolated work environments. History is a record of decisions — make it worth reading.
main is always deployableBranch naming:
feature/descriptionfix/descriptionchore/descriptionDelete branches after merging.
Each commit accomplishes one logical task.
Good:
feat: add hero section animation on scroll
fix: correct contact form link in header
test: add unit tests for cn() utility
Bad:
various changes
update stuff
wip
type: short description (≤ 72 chars)
[optional body explaining WHY, not what]
[reference issue or PR if relevant]
Types: feat, fix, refactor, test, docs, chore, style, perf
Explain why a change exists, not just what it does. The diff shows the what; the message should capture the reasoning.
Make a change → test it → commit if successful → revert if it fails. Never lose more than one increment of work.
Before every commit:
git diff --cached | grep -i "password\|secret\|api_key\|token" — no secretsnpm run lint)A good PR description includes:
This helps reviewers understand scope decisions without guessing.
Target ~100 lines changed per commit. Up to 300 is acceptable for a single logical change. Above 1000 lines, split into smaller commits.
.env filesgit push --force on shared branchesEvaluate code changes across five dimensions before merge. Approve changes that improve overall code health, even if not perfect.
Reduce complexity while preserving identical behavior. The goal is comprehension speed, not line reduction.
Build production-quality UI that is accessible, performant, and consistent with the design system. Not AI-generated-looking.
Search tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip — web APIs evolve rapidly and training weights contain obsolete patterns. Trigger immediately for: - UI/Layout: Modals, dialogs, popovers, Glassmorphism/backdrop-filters, anchor positioning, container queries, `:has()`, `:user-valid`. - Scroll/Motion: View Transitions, Scroll-driven animations, scroll parallax/reveals. - Performance: CWV (LCP, INP), content-visibility, Fetch Priority, image optimization. - System/APIs: Local filesystem access, WebUSB, WebSockets sync, WebAssembly widgets. - Frameworks: Adapting layout/styles in React, Vue, Angular. - General Frontend: Forms, autofill, advanced inputs, custom scrollbars, modern component states, etc. DO NOT trigger for: - Backend: Database SQL, ORMs, Express API routes. - Pipelines: CI/CD deployment, Docker, Actions. - Generic: Local scripts (Python/Go tools), ESLint, Git.
Measure before optimizing. Performance work without measurement is guessing.
Decompose work into small, verifiable, dependency-ordered tasks. Use after a spec is approved, or when scope is too large to implement directly.