一键在 Manus 中运行任何 Skill

commit

星标9

分支1

更新时间2026年5月1日 23:36

Analiza los cambios en el stage, ejecuta validaciones previas y realiza un commit siguiendo el estándar de Conventional Commits del equipo con emojis.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

weincoder

weincoder/valora-code

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

🤖 SKILL INSTRUCTIONS: TEAM COMMIT STANDARD

🎯 AGENT BEHAVIOR (HOW TO EXECUTE)

When the user asks you to commit the current changes, you MUST follow this exact sequence:

Validate: Run dart analyze to ensure there are no errors or warnings. If issues exist, fix them first.
Test: Run flutter test to ensure no tests are broken.
Stage: Run git add . (or stage the specific files requested).
Analyze Diff: Review the staged changes to understand WHAT was changed and WHY.
Commit: Execute the git commit -m "..." command using the STRICT template below.

🛑 1. COMMIT MESSAGE TEMPLATE

You MUST strictly format the commit message as follows:

<type>(<scope>): <emoji> <Subject line (max 50 chars)>

<Body (MINIMUM 150 characters). Explain in detail WHAT was changed and WHY. Give context to the team.>

Componentes afectados:
- <component_1>
- <component_2>

🏷️ 2. ALLOWED TYPES AND EMOJIS

You MUST choose exactly ONE type and its corresponding emoji from this list:

feat: 🆕 (New feature)
fix: 🔨 (Bug fix)
chore: 🧹 (Routine tasks, dependencies, etc.)
docs: 📓 (Documentation changes)
test: 🧪 (Adding or fixing tests)
style: 🎨 (Formatting, missing semi colons, etc; no code change)
refactor: 🏗️ (Code change that neither fixes a bug nor adds a feature)
perf: 🛠️ (Code change that improves performance)
build: 🧱 (Changes that affect the build system)
ci: ⚙️ (Changes to our CI configuration files and scripts)
revert: ⚠️ (Reverts a previous commit)

📋 3. EXAMPLE OF A VALID COMMIT

feat(auth): 🆕 Implement login screen with Google provider

Se implementó la pantalla de inicio de sesión utilizando la arquitectura limpia previamente definida. Se agregaron los adaptadores para Google SignIn y se conectó el caso de uso principal con la capa de presentación. Esto resuelve el requerimiento del negocio para permitir el acceso rápido de nuevos usuarios sin necesidad de crear contraseñas manuales.

Componentes afectados:
- lib/ui/pages/login_page.dart
- lib/infrastructure/driven_adapters/auth_api.dart
- lib/domain/usecase/auth_use_case.dart

✅ 4. PRE-OUTPUT CHECKLIST

Before committing, ensure internally:

Did I run dart analyze and flutter test?
Is the subject line under 50 characters?
Is the body description AT LEAST 150 characters?
Did I use the correct <type> and <emoji>?

同仓库更多 Skills

同仓库

flutter-use-http-package

weincoder/valora-code

Use the `http` package to execute GET, POST, PUT, or DELETE requests. Use when you need to fetch from or send data to a REST API.

2026-05-119

dart-analyze

weincoder/valora-code

Ejecuta el análisis estático de Dart/Flutter y resuelve los issues y advertencias encontrados siguiendo las reglas de analysis_options.yaml y las prácticas del equipo

2026-05-019

dart-testing

weincoder/valora-code

Genera unit tests y widget tests siguiendo el estándar del equipo (estructura AAA, groups por método, escenarios de error, convención de nombres y ubicación)

2026-05-019

flutter-json-backup

weincoder/valora-code

Implementa un sistema de respaldo y restauración en formato JSON local, siguiendo principios de Clean Architecture, serialización pura, compatibilidad cruzada e inmutabilidad.

2026-05-019

🤖 SKILL INSTRUCTIONS: TEAM COMMIT STANDARD

🎯 AGENT BEHAVIOR (HOW TO EXECUTE)

When the user asks you to commit the current changes, you MUST follow this exact sequence:

Validate: Run dart analyze to ensure there are no errors or warnings. If issues exist, fix them first.

Test: Run flutter test to ensure no tests are broken.

Stage: Run git add . (or stage the specific files requested).

Analyze Diff: Review the staged changes to understand WHAT was changed and WHY.

Commit: Execute the git commit -m "..." command using the STRICT template below.

🛑 1. COMMIT MESSAGE TEMPLATE

You MUST strictly format the commit message as follows:

<type>(<scope>): <emoji> <Subject line (max 50 chars)> <Body (MINIMUM 150 characters). Explain in detail WHAT was changed and WHY. Give context to the team.> Componentes afectados: - <component_1> - <component_2>

🏷️ 2. ALLOWED TYPES AND EMOJIS

You MUST choose exactly ONE type and its corresponding emoji from this list:

feat: 🆕 (New feature)

fix: 🔨 (Bug fix)

chore: 🧹 (Routine tasks, dependencies, etc.)

docs: 📓 (Documentation changes)

test: 🧪 (Adding or fixing tests)

style: 🎨 (Formatting, missing semi colons, etc; no code change)

refactor: 🏗️ (Code change that neither fixes a bug nor adds a feature)

perf: 🛠️ (Code change that improves performance)

build: 🧱 (Changes that affect the build system)

ci: ⚙️ (Changes to our CI configuration files and scripts)

revert: ⚠️ (Reverts a previous commit)

📋 3. EXAMPLE OF A VALID COMMIT

feat(auth): 🆕 Implement login screen with Google provider Se implementó la pantalla de inicio de sesión utilizando la arquitectura limpia previamente definida. Se agregaron los adaptadores para Google SignIn y se conectó el caso de uso principal con la capa de presentación. Esto resuelve el requerimiento del negocio para permitir el acceso rápido de nuevos usuarios sin necesidad de crear contraseñas manuales. Componentes afectados: - lib/ui/pages/login_page.dart - lib/infrastructure/driven_adapters/auth_api.dart - lib/domain/usecase/auth_use_case.dart

✅ 4. PRE-OUTPUT CHECKLIST

Before committing, ensure internally:

Did I run dart analyze and flutter test?

Is the subject line under 50 characters?

Is the body description AT LEAST 150 characters?

Did I use the correct <type> and <emoji>?

name	commit
description	Analiza los cambios en el stage, ejecuta validaciones previas y realiza un commit siguiendo el estándar de Conventional Commits del equipo con emojis.