一键在 Manus 中运行任何 Skill

开始使用

commit

星标0

分支0

更新时间2026年7月18日 07:48

Read this skill before making git commits

安装

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

在 Manus 中运行

来源

thekorn

thekorn/agent-skills

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

下载

在 Manus 中运行

Format

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

<optional body>

<optional footer>

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

Body is OPTIONAL for small, self-explanatory changes. For substantial changes, especially multiple related changes or changes whose rationale is not apparent from the summary, add a body explaining why the change was made and its important behavior. Use separate short paragraphs for distinct points.
Do NOT include breaking-change markers.
Footer is OPTIONAL unless the change addresses an issue or ticket, in which case it is REQUIRED and must reference the issue or ticket number.
Do NOT add sign-offs (no Signed-off-by).
Only commit; do NOT push.
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.
If the change is addressing an issue, include the issue number in the footer line.
- Fixes <issue> closes an issue when merged.
- Refs <issue> links an issue without closing it.

Steps

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review git status, git diff --no-ext-diff, and git diff --cached --no-ext-diff to understand the current changes (limit to argument-specified files if provided).
(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 the intended files (all changes if no files specified).
Run git commit -m "<summary>" (and -m "<body>" if needed) (and -m "<footer>" if needed).

Creating the Commit

Use separate -m arguments for paragraphs and footers. Never put literal \n sequences in a commit message or open an interactive editor.

git commit -m "fix(api): Handle null response in user endpoint" \
  -m "Return 404 when the user API finds a deleted account." \
  -m "Fixes XXX-12345"

同仓库更多 Skills

同仓库

ctf-sandbox-status

thekorn/agent-skills

Checks CTF sandbox availability for a Jira ticket ID by probing Vibe and brand endpoints (Bunte, Focus, Chip, Fit for fun). Use when the user asks for sandbox status, availability, or URLs for a ticket like TT-12345, FOL-234, or CTF-5634.

2026-07-210

html-diagram

thekorn/agent-skills

Create a self-contained HTML file for visualizing architecture and understanding the stack with a high-quality SVG diagram. Use when the user wants a full-screen diagram, wants the output to be light on prose, or wants an HTML artifact that is mostly there to make the architecture click fast.

2026-07-160

html-plan

thekorn/agent-skills

Create a self-contained HTML plan that is pragmatic, simple, and visually organized. Use when the user wants a plan page in the effective HTML style, wants the writing kept close to what they gave you, or wants the grammar cleaned up without turning it into a whole bigger thing.

2026-07-160

html

thekorn/agent-skills

Create a self-contained HTML file for whatever the user is describing, in the effective HTML style. Use when the user wants an HTML artifact that isn't specifically a diagram or a plan — a report, explainer, comparison, deck, prototype, or anything else best delivered as one HTML file.

2026-07-160

bun-development

thekorn/agent-skills

Fast, modern JavaScript/TypeScript development with the Bun runtime, inspired by [oven-sh/bun](https://github.com/oven-sh/bun).

2026-07-150

frontend-design

thekorn/agent-skills

Design and implement distinctive, production-ready frontend interfaces with strong aesthetic direction. Use when asked to create or restyle web pages, components, or applications (HTML/CSS/JS, React, Vue, etc.).

2026-07-150

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>

<optional body>

<optional footer>

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

Body is OPTIONAL for small, self-explanatory changes. For substantial changes, especially multiple related changes or changes whose rationale is not apparent from the summary, add a body explaining why the change was made and its important behavior. Use separate short paragraphs for distinct points.
Do NOT include breaking-change markers.
Footer is OPTIONAL unless the change addresses an issue or ticket, in which case it is REQUIRED and must reference the issue or ticket number.
Do NOT add sign-offs (no Signed-off-by).
Only commit; do NOT push.
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.
If the change is addressing an issue, include the issue number in the footer line.
- Fixes <issue> closes an issue when merged.
- Refs <issue> links an issue without closing it.

Steps

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review git status, git diff --no-ext-diff, and git diff --cached --no-ext-diff to understand the current changes (limit to argument-specified files if provided).
(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 the intended files (all changes if no files specified).
Run git commit -m "<summary>" (and -m "<body>" if needed) (and -m "<footer>" if needed).

Creating the Commit

Use separate -m arguments for paragraphs and footers. Never put literal \n sequences in a commit message or open an interactive editor.

git commit -m "fix(api): Handle null response in user endpoint" \
  -m "Return 404 when the user API finds a deleted account." \
  -m "Fixes XXX-12345"