commit
Commit Changes
Overview
Analyze the current git changes, group related files into meaningful commits, and create clean git commits. Each commit should represent a single logical change and stage only the files that belong to that change.
Commit Message Standard
Use a short, one-sentence commit message with a conventional prefix.
Allowed Prefixes
- Feat: introducing a new feature or capability
- Fix: bug fixes or behavior corrections
- Refactor: code restructuring without behavior change
- Chore: tooling, config, or maintenance work
- Docs: documentation-only changes
- Test: adding or updating tests
More from milistu/agent-skills
apple-human-interface-guidelines
Apple Human Interface Guidelines (HIG) reference for designing iOS, iPadOS, macOS, tvOS, visionOS, watchOS apps. Covers UI components, layout, accessibility, typography, navigation, inputs, and platform technologies. Use when designing Apple platform UIs, reviewing SwiftUI/UIKit patterns, or applying HIG design principles to any app.
50challenge-me
Direct technical advisor mode for counting/estimation and architecture/design
27pr-message
Write a concise, high-signal GitHub pull request message that explains intent, impact, and risk
26conventional-comments
Format review comments following the Conventional Comments standard. Use when writing code review comments, PR feedback, RFC reviews, peer reviews, or when the user asks for help with review comments.
25conventional-commits
Generate commit messages following the Conventional Commits v1.0.0 specification with Angular convention types. Use when creating git commits, writing commit messages, or when the user asks for help with commit messages.
24pr-review
Analyze and explain a pull request to help review it effectively
22