メニュー
Generate a copy-paste ready git commit message from staged changes (or unstaged changes if nothing is staged). Read-only — never stages, never commits. Triggers: commit, make commit, quick commit, git commit, create commit, commit message, generar commit.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | quick-commit |
| description | Generate a copy-paste ready git commit message from staged changes (or unstaged changes if nothing is staged). Read-only — never stages, never commits. Triggers: commit, make commit, quick commit, git commit, create commit, commit message, generar commit. |
This skill is read-only. It only inspects the working tree and generates a text block — it never stages files and never commits.
git status --short
git diff --cached --stat
git diff --cached
git log --oneline -5
If git diff --cached --stat returns nothing (no staged changes), also run:
git diff --stat
git diff
If no changes at all → abort with a message.
Analyze the diff and recent commits to understand project style. Generate a message following this format:
<type>: <imperative summary>
<optional body with motivation/context>
Types: feat, fix, refactor, chore, docs, style, test, perf
Rules:
feat/task-05-... → references task-05)Output only the commit message as a ready-to-copy block:
<type>: <summary>
<body>
Do not ask for confirmation, do not offer options, do not stage, do not commit.
| Mistake | Fix |
|---|---|
| Long summary line | Keep under 70 chars |
| Vague message | Be specific about what the change accomplishes |
| Portuguese in message | Write in English to match project convention |
Read the codebase knowledge graph for Stetsom Front. The graph lives in graphify-out/ and was generated by Claude Code. Use it for codebase orientation, impact analysis, and dependency tracing. VSCode agents cannot regenerate the graph — use /graphify in Claude Code CLI for that.
Full-site Figma fidelity audit for Stetsom Front. Downloads all page frames (desktop + mobile), performs cross-page divergence analysis with a ranked severity matrix, implements phased corrections, validates with tsc+lint, and exports baseline images. Use for periodic design audits, before major releases, or after big refactors. Trigger keywords: design audit, full design review, fidelity check, design fidelity, figma audit, audit figma, all pages review, full site audit.
Full-site Figma fidelity audit for Stetsom Front. Downloads all page frames (desktop + mobile), performs cross-page divergence analysis with a ranked severity matrix, implements phased corrections, validates with tsc+lint, and exports baseline images. Use for periodic design audits, before major releases, or after big refactors. Trigger keywords: design audit, full design review, fidelity check, design fidelity, figma audit, audit figma, all pages review, full site audit.
Audits screens/flows against Figma for completeness, correctness and consistency. Accepts any scope: a specific screen name, area ("cms", "admin", "website", "produtos"), or nothing (audits everything). Produces a ranked divergence matrix of missing flows, wrong fields, incorrect columns, broken UX, data model mismatches. Always presents the matrix to the user BEFORE implementing anything. Trigger keywords: screen audit, tela audit, audit screens, audit cms, audit website, audit flows, fluxo faltando, tela errada, validar telas, revisar telas, checar telas, missing screens, screen review, ux audit.
Refactor large or redundant code into modular, reusable components following Stetsom stack conventions (Next.js App Router, React 19, Tailwind v4, shadcn/ui). Use when files are too large, logic is duplicated, or components lack proper separation of concerns. Triggers: modularize, componentize, refactor, split component, extract component, reduce redundancy, cleanup code.
Design refinement pass using Figma MCP. Fetches live design from Figma (never local files), maps tokens, validates code against design standards, updates local context if stale, and produces an action plan via /next-task. Trigger keywords: refine design, figma alignment, design pass, design review, check design.