メニュー
This skill should be used when the user asks to "commit", "make a commit", "commit my changes", "create commits", "git commit", or wants to commit staged/unstaged changes with logical grouping and conventional commit format.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Search project documentation using qmd semantic search. Invoke with /avinyc:qmd-search <query> to find docs, plans, or indexed markdown content in your project.
Configure or reconfigure qmd collections for this project. Triggers on "configure qmd", "set up qmd", "reconfigure qmd", "qmd setup".
Run qmd health check for this project. Triggers on "qmd doctor", "check qmd health", "qmd problems", "diagnose qmd".
Show qmd configuration and index status for this project. Triggers on "qmd status", "show qmd config", "qmd collections".
Analyze completed development work to identify automation and systematization opportunities. Use after finishing features, fixing bugs, or completing code reviews. Triggers on "analyze for automation", "what can we automate", "compound opportunities", "systematize".
UX/UI design principles for clean, intuitive interfaces. Use when designing layouts, improving usability, planning information architecture, or ensuring accessibility. Triggers on "user experience", "usability", "information architecture", "accessibility", "interaction design".
| name | avinyc:commit |
| description | This skill should be used when the user asks to "commit", "make a commit", "commit my changes", "create commits", "git commit", or wants to commit staged/unstaged changes with logical grouping and conventional commit format. |
| user-invocable | true |
| argument-hint | [files or message] |
Analyze git changes and create logical, well-structured commits using conventional commit format.
Run git status to see all changes:
git status
Review both staged and unstaged changes. Identify modified, added, and deleted files.
Group changes into logical commits based on:
Present the commit plan to the user before proceeding:
I see the following logical commits:
1. feat(auth): Add password reset - auth/reset.rb, auth/mailer.rb
2. fix(api): Handle null responses - api/client.rb
3. docs: Update README - README.md
For each planned commit:
Stage specific files only:
git add <file1> <file2>
Verify staging:
git status
Create commit with conventional format:
git commit -m "<type>[scope]: <description>" -m "<body>"
Verify commit succeeded:
git status
Only proceed to the next commit after verifying the current one completed.
| Type | Description |
|---|---|
| feat | New feature |
| fix | Bug fix |
| docs | Documentation only |
| style | Formatting, no code change |
| refactor | Code change, no new feature or fix |
| perf | Performance improvement |
| test | Adding or fixing tests |
| chore | Build process, auxiliary tools |
<type>[optional scope]: <description>
[optional body]
[optional footer]
git add . or git add -A without explicit approval$ git status
# Modified: auth/login.rb, auth/signup.rb, README.md, api/client.rb
Plan:
1. feat(auth): Improve login validation - auth/login.rb, auth/signup.rb
2. fix(api): Handle timeout errors - api/client.rb
3. docs: Add authentication guide - README.md
Executing commit 1...
$ git add auth/login.rb auth/signup.rb
$ git status # verify only auth files staged
$ git commit -m "feat(auth): improve login validation" -m "Add email format check and rate limiting"
$ git status # verify commit succeeded
Executing commit 2...
[continues...]