Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

gh-commit

Étoiles1

Forks0

Mis à jour17 mars 2026 à 07:57

Auto-analyze git changes and generate Conventional Commits messages. Use when need to commit changes with proper commit messages. Triggers on "提交", "commit", "gh-commit", "/gh-commit", "自動 commit".

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

panda850819

panda850819/skm

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	gh-commit
description	Auto-analyze git changes and generate Conventional Commits messages. Use when need to commit changes with proper commit messages. Triggers on "提交", "commit", "gh-commit", "/gh-commit", "自動 commit".
allowed-tools	Bash, Read, Glob, Grep
version	1.0.0
scope	public
evolution	{"enabled":true,"version":"1.0.0","stability":"stable","auto_evolve":"patch","created":"2026-02-12T00:00:00.000Z","updated":"2026-02-12T00:00:00.000Z","history":[{"version":"1.0.0","date":"2026-02-12","note":"Split from gh-commit-and-push"}]}

GH Commit

Automatically analyze project changes, generate structured commit messages, and execute git add + commit.

Methodology:

Conventional Commits - Structured format, supports automation tools
Chris Beams' Seven Rules - Readability, imperative mood, 50-character limit

Integrations

upstream:
  - context: git working directory
    receives: Uncommitted changes

downstream:
  - skill: gh-push
    produces: Committed but unpushed commits

Out of Scope

Push to remote - Use gh-push
Complex merge conflicts - Requires manual handling
Rebase or amend - Only performs simple add/commit
Splitting into multiple commits - Commits all changes at once

When to Use

Finished a feature or fix, need to commit quickly
Want auto-generated commit messages following conventions
Team project requires unified commit format

Workflow

Phase 0: Identity Verification

Confirm git identity matches directory
```
git config user.name && git config user.email
```
Automatically determine expected identity based on directory (handled by .gitconfig includeIf):

Path Name Email
~/work/ pdyei panda@yei.finance
~/personal/, ~/site/ panda850819 pandap.d819@gmail.com
- If actual identity does not match expected, warn the user and pause
- Display: Committing as [name] <[email]>

Phase 1: Check Status

Run git status
```
git status --short
```
- If no changes, notify the user and stop
Check current branch
```
git branch --show-current
```

Phase 2: Analyze Change Types

Get detailed changes

git diff --stat
git diff --cached --stat
git status --short

Classify changed files

File Pattern	Type	Description
`README.md`, `.md` (docs/)	`docs`	Documentation changes
`test/`, `.test.js`, `.spec.js`	`test`	Test-related
`.gitignore`, `package.json`, `*.config.js`	`chore`	Configuration, dependency management
New files (multiple)	`feat`	New feature
Modified existing files (bug-related)	`fix`	Bug fix
Modified existing files (restructuring)	`refactor`	Refactoring
Styling, formatting	`style`	Format adjustments

Smart primary type detection
- Priority order: feat > fix > refactor > docs > test > chore

Phase 3: Determine Project Language

Language detection rules

Condition Language Choice
README is mainly Chinese Chinese
README is mainly English + has team markers English
No README or personal project markers Chinese
.claude directory exists with Chinese docs Chinese

Phase 4: Generate Commit Message

Compose Commit Message

Format (Conventional Commits):
```
<type>(<scope>): <subject>

<body>
```
Rules (Chris Beams):
- Subject limited to 50 characters (25 Chinese characters)
- Use imperative mood
- Capitalize first letter
- No trailing period
- Body explains what and why — must state the motivation/reason, not just list files changed. Ask: "Why was this change necessary?" If body only describes what (e.g., "Modified auth.ts"), it is incomplete.

Phase 5: Execute Git Operations

Add all changes
```
git add .
```
Commit with message
```
git commit -m "<generated message>"
```

Type Classification Reference

Conventional Commits Types

Type	Usage	Examples
`feat`	New feature	Add API endpoint, add UI component
`fix`	Bug fix	Fix calculation error, fix UI display issue
`docs`	Documentation	Update README, add comments
`style`	Formatting	Adjust indentation, remove blank lines
`refactor`	Refactoring	Extract function, reorganize file structure
`perf`	Performance	Optimize queries, reduce memory usage
`test`	Testing	Add tests, modify tests
`build`	Build system	Modify webpack config
`ci`	CI/CD	Modify GitHub Actions
`chore`	Miscellaneous	Update dependencies, modify .gitignore

Decision Flowchart

File changes
   |
New file?
   |-- Yes -> feat (new feature)
   +-- No  |
What type of file was modified?
   |-- README/docs -> docs
   |-- test files -> test
   |-- config files -> chore
   +-- source code |
         Commit message or diff contains "fix", "bug"?
            |-- Yes -> fix
            +-- No  -> refactor or feat (based on scope of change)

Safety and Escalation

Situation	Action
No uncommitted changes	Notify user, stop
Merge conflicts exist	Prompt user to handle manually
Not a git repository	Prompt to initialize git

Verification

# Confirm last commit
git log -1 --oneline

# Confirm commit details
git show HEAD

Methodology Sources

Conventional Commits: https://www.conventionalcommits.org/
Chris Beams' Seven Rules: https://cbea.ms/git-commit/

Plus depuis ce dépôt

même dépôt

skills-audit

panda850819/skm

Comprehensive health check of Claude Code skill ecosystem — cross-check registry.yaml, disk, symlinks, INDEX.md, and frontmatter validation. Use after skill restructuring or periodically.

2026-03-171

settings-security-audit

panda850819/skm

Audit Claude Code settings.json for security vulnerabilities — detect allow-bypasses-deny, missing sensitive file denies, and overly broad permissions. Use after any settings.json change.

2026-03-171

pdf

panda850819/skm

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

2026-03-171

ui-ux-pro-max

panda850819/skm

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

2026-03-171

peon-ping-toggle

panda850819/skm

Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session.

2026-03-171

prefer-pnpm

panda850819/skm

Use when installing packages, adding dependencies, or running package manager commands. Triggers on npm install, npm add, package installation, dependency management.

2026-03-171

name	gh-commit
description	Auto-analyze git changes and generate Conventional Commits messages. Use when need to commit changes with proper commit messages. Triggers on "提交", "commit", "gh-commit", "/gh-commit", "自動 commit".
allowed-tools	Bash, Read, Glob, Grep
version	1.0.0
scope	public
evolution	{"enabled":true,"version":"1.0.0","stability":"stable","auto_evolve":"patch","created":"2026-02-12T00:00:00.000Z","updated":"2026-02-12T00:00:00.000Z","history":[{"version":"1.0.0","date":"2026-02-12","note":"Split from gh-commit-and-push"}]}

GH Commit

Automatically analyze project changes, generate structured commit messages, and execute git add + commit.

Methodology:

Conventional Commits - Structured format, supports automation tools
Chris Beams' Seven Rules - Readability, imperative mood, 50-character limit

Integrations

upstream:
  - context: git working directory
    receives: Uncommitted changes

downstream:
  - skill: gh-push
    produces: Committed but unpushed commits

Out of Scope

Push to remote - Use gh-push
Complex merge conflicts - Requires manual handling
Rebase or amend - Only performs simple add/commit
Splitting into multiple commits - Commits all changes at once

When to Use

Finished a feature or fix, need to commit quickly
Want auto-generated commit messages following conventions
Team project requires unified commit format

Workflow

Phase 0: Identity Verification

Confirm git identity matches directory
```
git config user.name && git config user.email
```
Automatically determine expected identity based on directory (handled by .gitconfig includeIf):

Path Name Email
~/work/ pdyei panda@yei.finance
~/personal/, ~/site/ panda850819 pandap.d819@gmail.com
- If actual identity does not match expected, warn the user and pause
- Display: Committing as [name] <[email]>

Phase 1: Check Status

Run git status
```
git status --short
```
- If no changes, notify the user and stop
Check current branch
```
git branch --show-current
```

Phase 2: Analyze Change Types

Get detailed changes

git diff --stat
git diff --cached --stat
git status --short

Classify changed files

File Pattern	Type	Description
`README.md`, `.md` (docs/)	`docs`	Documentation changes
`test/`, `.test.js`, `.spec.js`	`test`	Test-related
`.gitignore`, `package.json`, `*.config.js`	`chore`	Configuration, dependency management
New files (multiple)	`feat`	New feature
Modified existing files (bug-related)	`fix`	Bug fix
Modified existing files (restructuring)	`refactor`	Refactoring
Styling, formatting	`style`	Format adjustments

Smart primary type detection
- Priority order: feat > fix > refactor > docs > test > chore

Phase 3: Determine Project Language

Language detection rules

Condition Language Choice
README is mainly Chinese Chinese
README is mainly English + has team markers English
No README or personal project markers Chinese
.claude directory exists with Chinese docs Chinese

Phase 4: Generate Commit Message

Compose Commit Message

Format (Conventional Commits):
```
<type>(<scope>): <subject>

<body>
```
Rules (Chris Beams):
- Subject limited to 50 characters (25 Chinese characters)
- Use imperative mood
- Capitalize first letter
- No trailing period
- Body explains what and why — must state the motivation/reason, not just list files changed. Ask: "Why was this change necessary?" If body only describes what (e.g., "Modified auth.ts"), it is incomplete.

Phase 5: Execute Git Operations

Add all changes
```
git add .
```
Commit with message
```
git commit -m "<generated message>"
```

Type Classification Reference

Conventional Commits Types

Type	Usage	Examples
`feat`	New feature	Add API endpoint, add UI component
`fix`	Bug fix	Fix calculation error, fix UI display issue
`docs`	Documentation	Update README, add comments
`style`	Formatting	Adjust indentation, remove blank lines
`refactor`	Refactoring	Extract function, reorganize file structure
`perf`	Performance	Optimize queries, reduce memory usage
`test`	Testing	Add tests, modify tests
`build`	Build system	Modify webpack config
`ci`	CI/CD	Modify GitHub Actions
`chore`	Miscellaneous	Update dependencies, modify .gitignore

Decision Flowchart

File changes
   |
New file?
   |-- Yes -> feat (new feature)
   +-- No  |
What type of file was modified?
   |-- README/docs -> docs
   |-- test files -> test
   |-- config files -> chore
   +-- source code |
         Commit message or diff contains "fix", "bug"?
            |-- Yes -> fix
            +-- No  -> refactor or feat (based on scope of change)

Safety and Escalation

Situation	Action
No uncommitted changes	Notify user, stop
Merge conflicts exist	Prompt user to handle manually
Not a git repository	Prompt to initialize git

Verification

# Confirm last commit
git log -1 --oneline

# Confirm commit details
git show HEAD

Methodology Sources

Conventional Commits: https://www.conventionalcommits.org/
Chris Beams' Seven Rules: https://cbea.ms/git-commit/

Path	Name	Email
`~/work/`	pdyei	panda@yei.finance
`~/personal/`, `~/site/`	panda850819	pandap.d819@gmail.com

Condition	Language Choice
README is mainly Chinese	Chinese
README is mainly English + has team markers	English
No README or personal project markers	Chinese
.claude directory exists with Chinese docs	Chinese