- SKILL.md 110 lines · 3.2 KB
Smart Commit
Create meaningful conventional commits by analyzing your actual changes.
Workflow
Step 1: Assess the working tree
Run these commands to understand the current state:
git status
git diff --stat
git diff --cached --statStep 2: Handle unstaged changes
If nothing is staged (git diff --cached is empty):
- Show the user what files have changed
- Suggest what to stage based on logical grouping (e.g., "these 3 files are all related to the auth refactor")
- Ask if they want to stage all, or select specific files
- Stage the approved files with
git add <files>
If changes are already staged, proceed to analysis.
Step 3: Analyze the diff
Read the full staged diff:
git diff --cachedDetermine the commit type from the changes:
| Signal | Type |
|---|---|
| New files with new functionality | feat |
| New test files or test additions | test |
| Changes to existing logic fixing incorrect behavior | fix |
| Structural changes without behavior change | refactor |
| package.json, tsconfig, CI config changes | chore |
| Build/bundler config changes | build |
| README, docs, comments only | docs |
| Formatting, whitespace, semicolons only | style |
| Performance improvements | perf |
Determine the scope from the primary directory or module affected:
src/api/->apisrc/components/auth/->authtests/->tests- Root config files -> omit scope
- Multiple unrelated areas -> omit scope
Step 4: Check for user overrides
If the user provided arguments via $ARGUMENTS:
- Single word (e.g.,
fix) -> use as commit type - Two words (e.g.,
refactor api) -> use as type and scope - Otherwise -> use auto-detected values
Step 5: Compose the commit message
Format: type(scope): imperative short description
Rules:
- Subject line max 72 characters
- Use imperative mood ("add", "fix", "refactor", not "added", "fixes")
- Don't end with a period
- Body explains WHY this change was made, not what changed (the diff shows what)
- If changes are trivial (typo fix, formatting), skip the body
Example:
feat(auth): add JWT refresh token rotation
Tokens were expiring mid-session for users with slow connections.
Rotating refresh tokens extends the session without compromising
security, since each refresh token can only be used once.Step 6: Confirm and commit
Show the user the proposed commit message and ask for confirmation.
If confirmed, run:
git commit -m "<message>"Then verify with:
git log --oneline -1Show the committed hash and message.
Tips
- Run after completing a logical unit of work, not after every file change
- If the diff is too large for one commit, suggest splitting into multiple commits
- For breaking changes, add
!after the scope:feat(api)!: change response format - The body should answer "if someone reads this commit in 6 months, will they understand WHY?"
Scanned by
NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-11-19
1 observation in 1 category
- Trigger Abuse 1
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them. Open one to see the lines it points at.
Shadow Command TriggerTrigger Abuse · SKILL.md:1
| 1 | --- |
| 2 | name: commit-smart |
| 3 | description: Analyze staged/unstaged changes and create semantic conventional commits with context about WHY, not just WHAT. Auto-detects commit type and scope from the diff. Supports optional type/scope arguments. Usage - /commit-smart, /c |
Learn more about NVIDIA SkillSpector or how components are reviewed.
Agent compatibility
Checked by NVIDIA SkillEvaluator Harness Check · v1.0.1 · 2026-11-18
How each agent reads this skill once it is installed, from the agents' documented loading rules. No agent was run. A note means the agent loads the skill but changes part of its text, or drops it.
Claude Code
loadsCodex
loads · 1 noteCopilot CLI
loads · 1 noteOpenCode
loads · 1 noteHermes
loads · 1 noteOpenClaw
loads · 1 note
Codex · loads with changes
$ARGUMENTS is not substituted: the model sees the literal text.
Fix: Describe the expected input in words instead of $ARGUMENTS.
CX-ARGUMENTS · verified on 0.166.0
Copilot CLI · loads with changes
$ARGUMENTS is not substituted: the model sees the literal text.
Fix: Describe the expected input in words instead of $ARGUMENTS.
CP-ARGUMENTS · verified on 1.0.105
OpenCode · loads with changes
Loaded through the skill tool, $ARGUMENTS is not substituted: the model sees the literal text (a /command run substitutes it).
Fix: Describe the expected input in words instead of $ARGUMENTS.
OC-ARGUMENTS · verified on 1.19.5
Hermes · loads with changes
$ARGUMENTS is not substituted: the model sees the literal text.
Fix: Describe the expected input in words instead of $ARGUMENTS.
HM-ARGUMENTS · verified on main
OpenClaw · loads with changes
$ARGUMENTS is not substituted: the model sees the literal text.
Fix: Describe the expected input in words instead of $ARGUMENTS.
OW-ARGUMENTS · verified on 2026.10.9
Learn more about NVIDIA SkillEvaluator.