commit
Create a git commit with a properly formatted message following the project's commit convention. Reads staged changes and generates a subject line with the correct prefix (feat:, fix:, refactor:, test:, docs:, chore:, задача:). Use when you are ready to commit completed work.
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-15
- Stars
- ★ 15
- Forks
- 1
01 前言 Front Matter
- name
- commit
- metadata
- { "short-description": "Commit staged changes with a correctly formatted message" }
- description
- Create a git commit with a properly formatted message following the project's commit convention. Reads staged changes and generates a subject line with the correct prefix (feat:, fix:, refactor:, test:, docs:, chore:, задача:). Use when you are ready to commit completed work.
03 SKILL.md 正文
<objective> Read the current git state, generate a commit message that matches the project's commit convention, confirm with the user if needed, and create the commit.
Project convention (from AGENTS.md):
- Use short imperative subject lines
- Prefix with: feat:, fix:, refactor:, test:, docs:, chore:, задача:
- Example: "feat: add primitiveSmelt actor and HSM wiring"
- Example: "задача: wire anti-loop guard into AGENT_LOOP" </objective>
<context> Arguments: {{GSD_ARGS}}
Git state:
- Staged files: !
git diff --cached --name-only - Staged diff summary: !
git diff --cached --stat - Current branch: !
git branch --show-current - Last 3 commits (for style reference): !
git log --oneline -3</context>
<process>
-
Assess staged changes
- If nothing is staged, check
git statusand inform the user — do not proceed with an empty commit. - If
{{GSD_ARGS}}contains a commit message, use it directly (add prefix if missing). - Otherwise, derive the message from the staged diff.
- If nothing is staged, check
-
Choose the correct prefix
Change type Prefix New feature / capability feat:Bug fix fix:Refactor / cleanup, no behavior change refactor:Tests only test:Documentation only docs:Build, config, tooling chore:Task / milestone work (Russian context) задача: -
Draft the subject line
- ≤ 72 characters
- Imperative mood ("add", "fix", "wire", not "added" or "adds")
- No period at the end
-
Add optional body (only if the change is non-trivial)
- Blank line after subject
- Explain what changed and why, not how
-
Execute the commit
git commit -m "<subject>" [-m "<body>"] -
Confirm — report the full commit hash and subject line after success. </process>
04 同仓库更多 Skills
deploy-app
Deploy the application to staging or production environments.
deploy
Deploy the application to environments.
building-native-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
create-section
Use when creating a new section for the AI Workshop presentation. Guides through title slide setup, layout choices, and content gathering. Activates when user wants to add a new topic section to the slideshow.
ship-checker
Run a full pre-ship review for this repo. Use when asked if a change is ready to deploy, publish, or ship.
lint-check
Run repository linters and report failures.