commit

Estrelas5

Forks0

Atualizado7 de julho de 2026 às 16:48

Stage the intended changes only, derive a scoped conventional-commit message, branch first if on main, run the staged lint check, and commit. Use when the user asks to commit work.

Instalação

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ê.

Executar no Manus

Fonte

tum-ai

tum-ai/member-manager

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	commit
description	Stage the intended changes only, derive a scoped conventional-commit message, branch first if on main, run the staged lint check, and commit. Use when the user asks to commit work.

/commit

Commit the current work cleanly.

Inspect — git status and git diff (and git diff --staged). Identify only the changes that belong to this unit of work. Do not blindly git add -A unrelated files.
Branch if on main — git branch --show-current. If it's main, create a topic branch first (git switch -c <type>/<short-slug>); never commit straight to main.
Stage the intended files explicitly (git add <paths>).
Lint staged — pnpm lint:staged. Fix anything it flags before committing.
Message — conventional commit, scoped: type(scope): summary where type ∈ feat|fix|refactor|test|ci|docs|style|chore|perf|build. Keep the subject imperative and concise.
Commit — do not add tool-specific co-author trailers unless explicitly requested. (The git-guard hook warns on non-conventional messages.)
Report the branch + short SHA. Don't push unless asked.

Mais deste repositório

mesmo repositório

gate

tum-ai/member-manager

Run the full pre-push gate (lint, typecheck, test, build) and triage any failures by stage. Use before pushing or when asked to verify the repo is green.

2026-07-075

new-feature

tum-ai/member-manager

Scaffold a new client feature folder following the Page→hook→sections pattern, using features/tools as the template. Use when starting a new client feature.

2026-07-075

pr-review

tum-ai/member-manager

Review a pull request against member-manager's invariants and post inline comments. Use when asked to review a PR.

2026-07-075

verify-e2e

tum-ai/member-manager

Reset and seed the local Supabase stack, then run the Playwright E2E suite (or a single spec) and summarize failures. Use when asked to verify end-to-end behavior.

2026-07-075

tumai-ci

tum-ai/member-manager

Use when changing UI, styling, theming, logos, imagery, or visual copy in this repo so the result follows the TUM.ai corporate identity. Apply the vendored brand guide, color system, typography, button treatment, and dark/light mode rules before shipping frontend work.

2026-03-305

name	commit
description	Stage the intended changes only, derive a scoped conventional-commit message, branch first if on main, run the staged lint check, and commit. Use when the user asks to commit work.

/commit

Commit the current work cleanly.

Inspect — git status and git diff (and git diff --staged). Identify only the changes that belong to this unit of work. Do not blindly git add -A unrelated files.
Branch if on main — git branch --show-current. If it's main, create a topic branch first (git switch -c <type>/<short-slug>); never commit straight to main.
Stage the intended files explicitly (git add <paths>).
Lint staged — pnpm lint:staged. Fix anything it flags before committing.
Message — conventional commit, scoped: type(scope): summary where type ∈ feat|fix|refactor|test|ci|docs|style|chore|perf|build. Keep the subject imperative and concise.
Commit — do not add tool-specific co-author trailers unless explicitly requested. (The git-guard hook warns on non-conventional messages.)
Report the branch + short SHA. Don't push unless asked.