تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

commit

النجوم١١

التفرعات٤

آخر تحديث١٠ أبريل ٢٠٢٦ في ١٥:٤٠

Read this skill before making git commits

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

aretw0

aretw0/agents-lab

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	commit
description	Read this skill before making git commits

Create a git commit for the current changes using a concise Conventional Commits-style subject.

Format

<type>(<scope>): <summary>

type REQUIRED. Use feat for new features, fix for bug fixes. Other types: docs, refactor, chore, test, perf, style, ci.
scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, auth, ui, cli).
summary REQUIRED. Short, imperative, lowercase, ≤ 72 chars, no trailing period.

Rules

Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs.
Do NOT include breaking-change markers or footers.
Do NOT add sign-offs (Signed-off-by).
Only commit — do NOT push.
Always pass the message on the command line, never rely on an interactive editor:
```
git commit -m "fix(auth): handle expired token on refresh"
```
If it is unclear which files to include, ask before staging.
Treat caller-provided arguments as additional commit guidance:
- Freeform text → influences scope, summary, and body
- File paths/globs → limit which files to stage and commit
- Combined → honor both

Steps

Check if the user provided specific file paths/globs and/or instructions.
Run git status and git diff to understand current changes.
(Optional) Run git log -n 20 --pretty=format:%s to see commonly used scopes in this project.
Ask for clarification if there are ambiguous extra files.
Stage only the intended files.
Run git commit -m "<subject>" (add -m "<body>" if a body is needed).

المزيد من هذا المستودع

نفس المستودع

pi-workflows-sovereign

aretw0/agents-lab

First-party, sovereign workflows form — author, list, and validate multi-step workflow specs (YAML, DAG of block/command/agent steps with typed I/O). Use when writing or checking .workflows/*.workflow.yaml. Execution (running workflows) is delivered by SP2; this slice provides the form (workflow_list, workflow_validate).

2026-06-2311

colony-dogfood

aretw0/agents-lab

Conduz um experimento de dogfood onde a colônia Pi executa uma task do .project/tasks.json em dois tempos (research → código) com gates do operador. Use quando o operador quiser ativar um experimento colony-experiment-phase1 ou colony-experiment-phase2.

2026-06-1811

control-plane-continuity

aretw0/agents-lab

Use when a Pi session needs to continue local-safe work with low operator friction: discover focus, interview only for missing constraints, prepare bounded slices, use workers only behind gates, checkpoint, and stop on real risk.

2026-05-2711

web-browser

aretw0/agents-lab

Interact with web pages via browser automation: navigate, click, fill forms, screenshot, and evaluate JavaScript. Uses Chrome/Chromium remote debugging (CDP).

2026-05-2311

control-plane-ops

aretw0/agents-lab

Operar o control-plane local-first do agents-lab com board canônico, long-runs bounded, handoff/checkpoint, rollout/rollback e espelhos externos sem perder governança.

2026-05-2211

cultivate-primitive

aretw0/agents-lab

Guia o cultivo de uma primitiva reutilizável. Use quando o usuário identificar um padrão recorrente que merece ser extraído como skill, extensão ou convenção.

2026-05-2211

name	commit
description	Read this skill before making git commits

Create a git commit for the current changes using a concise Conventional Commits-style subject.

Format

<type>(<scope>): <summary>

type REQUIRED. Use feat for new features, fix for bug fixes. Other types: docs, refactor, chore, test, perf, style, ci.
scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, auth, ui, cli).
summary REQUIRED. Short, imperative, lowercase, ≤ 72 chars, no trailing period.

Rules

Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs.
Do NOT include breaking-change markers or footers.
Do NOT add sign-offs (Signed-off-by).
Only commit — do NOT push.
Always pass the message on the command line, never rely on an interactive editor:
```
git commit -m "fix(auth): handle expired token on refresh"
```
If it is unclear which files to include, ask before staging.
Treat caller-provided arguments as additional commit guidance:
- Freeform text → influences scope, summary, and body
- File paths/globs → limit which files to stage and commit
- Combined → honor both

Steps

Check if the user provided specific file paths/globs and/or instructions.
Run git status and git diff to understand current changes.
(Optional) Run git log -n 20 --pretty=format:%s to see commonly used scopes in this project.
Ask for clarification if there are ambiguous extra files.
Stage only the intended files.
Run git commit -m "<subject>" (add -m "<body>" if a body is needed).