Skip to content
cccskills
FreePublished on 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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

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

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

  1. Categorize Changes: Identify what changed (new files, modifications, deletions)
  2. Determine Type: Is this a feature, fix, refactor, etc.?
  3. Identify Scope: What component/module is affected?
  4. 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:

  1. Run git status and git diff to understand changes
  2. Analyze the nature of changes
  3. Generate appropriate commit message
  4. Stage files if needed
  5. Create commit and report success

Example 2: Specific Type

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

Expected Behavior:

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace442Updated Oct 21, 2026

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.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace442Updated Oct 21, 2026

Systematic framework for extracting actionable items from documents and organizing them into prioritized, trackable checklists. Use when converting reports, meeting notes, audits, or any document with embedded action items into structured TODO lists.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace442Updated Oct 21, 2026

Browser automation for AI agents via inference.sh. Navigate web pages, interact with elements using @e refs, take screenshots, record video. Capabilities: web scraping, form filling, clicking, typing, drag-drop, file upload, JavaScript execution. Use for: web automation, data extraction, testing, agent browsing, research. Triggers: browser, web automation, scrape, navigate, click, fill form, screenshot, browse web, playwright, headless browser, web agent, surf internet, record video

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace442Updated Oct 21, 2026

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace442Updated Oct 21, 2026

Run AI apps via inference.sh CLI - image generation, video creation, LLMs, search, 3D, Twitter automation. Models: FLUX, Veo, Gemini, Grok, Claude, Seedance, OmniHuman, Tavily, Exa, OpenRouter, and many more. Use when running AI apps, generating images/videos, calling LLMs, web search, or automating Twitter. Triggers: inference.sh, infsh, ai model, run ai, serverless ai, ai api, flux, veo, claude api, image generation, video generation, openrouter, tavily, exa search, twitter api, grok

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace442Updated Oct 21, 2026

See all skills by aiskillstore

Report a problem with this skill