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

git-commit

النجوم١

التفرعات٠

آخر تحديث٢٢ فبراير ٢٠٢٦ في ١٧:١٧

Mandatory read before creating git commits. Stages only intended files, groups changes into logical commits, and writes concise Conventional Commits-style subjects.

التثبيت

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

تشغيل في Manus

المصدر

default-anton

default-anton/jagc

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

تنزيل

تشغيل في Manus

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

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

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

SKILL.md

readonly

name	git-commit
description	Mandatory read before creating git commits. Stages only intended files, groups changes into logical commits, and writes concise Conventional Commits-style subjects.

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 common types: docs, refactor, chore, test, perf.
scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).
summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.

Notes

Keep commits logically grouped: one commit = one cohesive, reviewable change.
If current changes mix unrelated work, split into multiple commits with selective staging.
"commit all" means stage all relevant files, not "force one commit".
If multiple logical groups exist and user did not request a squash, create multiple commits.
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 (no Signed-off-by).
Only commit; do NOT push (unless explicitly asked).
If it is unclear whether a file should be included, ask the user which files to commit.
Treat any caller-provided arguments as additional commit guidance. Common patterns:
- Freeform instructions should influence scope, summary, and body.
- File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise.
- If arguments combine files and instructions, honor both.

Steps

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review git status and git diff to understand the current changes (limit to argument-specified files if provided).
Partition changes into logical commit groups by intent and cohesion; use the smallest reviewable units.
If user asked to "commit all" and multiple groups exist, split into multiple commits by default; ask when grouping is ambiguous.
(Optional) Run git log -n 50 --pretty=format:%s to see commonly used scopes.
If there are ambiguous extra files, ask the user for clarification before committing.
Stage only files for the current logical commit (all changes only when they form one cohesive group and no files were specified).
Run git diff --cached --name-only to verify staged files match one logical group.
Run git commit -m "<subject>" (and -m "<body>" if needed).
Repeat staging/commit for remaining logical groups, if any.

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

نفس المستودع

agent-browser

default-anton/jagc

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

2026-02-181

task-ops

default-anton/jagc

Canonical jagc scheduled-task operations playbook. Use when the user asks for one-off or recurring scheduled work, asks to manage existing jagc tasks (create/list/get/update/delete/run/enable/disable), or when you want to suggest automating repeatable/future work as a task (get user approval first). Covers the exact `jagc task` command contract, JSON-first low-turn workflows, RRULE + one-off scheduling, deterministic relative-time -> UTC conversion, and verification policy.

2026-02-161

agents-md

default-anton/jagc

Use this skill before creating/modifying any `AGENTS.md` (including create/edit/move/split). It explains why AGENTS guidance should stay scoped and terse, when to edit root vs subtree files, and what content belongs in AGENTS.md.

2026-02-091

skills-md

default-anton/jagc

Use this skill before creating/modifying any skill (global, project, or package-level). It defines hard rules for writing tight, information-dense `SKILL.md` files, valid frontmatter, and when to move details into `references/` or `scripts/`.

2026-02-091

name	git-commit
description	Mandatory read before creating git commits. Stages only intended files, groups changes into logical commits, and writes concise Conventional Commits-style subjects.

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 common types: docs, refactor, chore, test, perf.
scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).
summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.

Notes

Keep commits logically grouped: one commit = one cohesive, reviewable change.
If current changes mix unrelated work, split into multiple commits with selective staging.
"commit all" means stage all relevant files, not "force one commit".
If multiple logical groups exist and user did not request a squash, create multiple commits.
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 (no Signed-off-by).
Only commit; do NOT push (unless explicitly asked).
If it is unclear whether a file should be included, ask the user which files to commit.
Treat any caller-provided arguments as additional commit guidance. Common patterns:
- Freeform instructions should influence scope, summary, and body.
- File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise.
- If arguments combine files and instructions, honor both.

Steps

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review git status and git diff to understand the current changes (limit to argument-specified files if provided).
Partition changes into logical commit groups by intent and cohesion; use the smallest reviewable units.
If user asked to "commit all" and multiple groups exist, split into multiple commits by default; ask when grouping is ambiguous.
(Optional) Run git log -n 50 --pretty=format:%s to see commonly used scopes.
If there are ambiguous extra files, ask the user for clarification before committing.
Stage only files for the current logical commit (all changes only when they form one cohesive group and no files were specified).
Run git diff --cached --name-only to verify staged files match one logical group.
Run git commit -m "<subject>" (and -m "<body>" if needed).
Repeat staging/commit for remaining logical groups, if any.