commit
Commit
Smart git commit workflow that protects important branches, writes good commit messages, and streamlines the commit-push cycle.
Workflow
Execute these steps in order. Gather information first, then act.
Step 1: Gather State
Run these commands in parallel to understand the current repo state:
| Command | Purpose |
|---|---|
git branch --show-current |
Current branch name |
git status --short |
Changed files overview |
git diff --stat |
Unstaged change summary |
git diff --cached --stat |
Staged change summary |
git log --oneline -5 |
Recent commit style reference |
More from jojious/ada-skills
brainstorm
>-
35improve
Iteratively improve any output until measurable criteria are met. Use when the user wants to refine existing work against specific standards — whether it's code, prose, data, config, or any other artifact. Triggers on phrases like "improve this", "make it better", "iterate", "refine", "keep improving", "not good enough yet", "optimize this", "polish this", "tighten this up", "ปรับปรุง", "ทำให้ดีขึ้น", "ยังไม่ดี", "แก้ให้ดีกว่านี้", "iterate ต่อ", or when the user provides criteria and wants repeated improvement until they're satisfied. Also use when the user gives feedback on output and expects you to keep refining, even if they don't say "improve" explicitly.
32api-doc-gen
>
11neo-team-kiro
>
7neo-team-claude
>
7confluence-api-doc
>
6