無料GitHub で公開

git-commit

Use this skill when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow.

aiskillstore/marketplace

インストール方法を見る

含まれるファイル（2）

SKILL.md2.6 KB
skill-report.json14.1 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Git Commit

Create well-structured git commits with conventional commit messages based on staged changes.

Parameters

{
  "type": "object",
  "properties": {
    "message": {
      "type": "string",
      "description": "Optional commit message override"
    },
    "type": {
      "type": "string",
      "enum": ["feat", "fix", "docs", "style", "refactor", "test", "chore"],
      "description": "Conventional commit type",
      "default": "auto"
    },
    "scope": {
      "type": "string",
      "description": "Optional scope for the commit"
    }
  }
}

When to Use

User asks to "commit" changes
User wants to "save" their work to git
User asks for help with commit messages
User wants to stage and commit files

Methodology

Phase 1: Status Check

Run git status to see current state
Run git diff --staged to see staged changes
Run git diff to see unstaged changes
Check recent commit history for message style

Phase 2: Analysis

Categorize Changes: Identify what changed (new files, modifications, deletions)
Determine Type: Is this a feature, fix, refactor, etc.?
Identify Scope: What component/module is affected?
Summarize Purpose: What does this change accomplish?

Phase 3: Commit Creation

Stage relevant files if not already staged
Generate conventional commit message
Execute the commit
Verify success with git status

Phase 4: Output

Report:

What was committed
The commit message used
The new commit hash

Guidelines

Follow Conventional Commits format: type(scope): description
Keep subject line under 72 characters
Use imperative mood ("Add feature" not "Added feature")
Don't commit sensitive files (.env, credentials, etc.)
Don't use --force or --amend unless explicitly requested
Include meaningful description of WHY, not just WHAT

Examples

Example 1: Auto Commit

User Input: "Commit my changes"

Expected Behavior:

Run git status and git diff to understand changes
Analyze the nature of changes
Generate appropriate commit message
Stage files if needed
Create commit and report success

Example 2: Specific Type

User Input: "创建一个 fix 类型的 commit"

Expected Behavior:

检查当前的改动
确认这些改动符合 "fix" 类型
生成格式为 fix(scope): 描述 的提交信息
执行提交并报告结果

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

acquisition-policy-workflow

無料

Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing prior policy analysis; or producing an Acquisition Policy Impact Brief. Use published federal sources and supplied policy documents without making legal or procurement-specific applicability determinations. Do not use for clause selection, market research execution, opportunities, pricing, grants, or cooperative agreements.

日本語の概要は準備中です。原文の説明を表示しています。