nsheaps/commit
plugins/scm-utils/skills/commit/SKILL.md
Intelligently commit outstanding changes in logical, focused commits. Use this when you want to commit code using git.
$ install --global
skillsauthnpx skillsauth add nsheaps/ai-mktpl commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 4:14 PM88.5s1 file scanned
SKILL.md
- name:
- commit
- description:
- Intelligently commit outstanding changes in logical, focused commits. Use this when you want to commit code using git.
- argument-hint:
- [optional hint]
Current branch status
!git status
last 10 commits
!git log --oneline -10
Intelligent Commit Process
You should commit outstanding changes by breaking them into logical, focused commits. The optional hint ($ARGUMENTS) provides guidance on what to commit, how to group changes, or what to emphasize in commit messages.
If the hint is unclear or ambiguous, ASK THE USER for clarification before proceeding.
Follow this iterative process:
Review Phase
- Check memory systems for commit strategies:
- Run
git statusto see all modified files - Run
git difffor each file to understand all changes - Run
git log --oneline -10to see recent commit message patterns - Run
gh pr viewto see if a PR exists for these changes and review its title and body - CRITICAL: Review ALL changes thoroughly to understand the goals and context
- CRITICAL: Consider the optional hint provided and how it should influence the commit strategy
- ASK THE USER about any changes you can't understand the purpose of - don't guess
- ASK THE USER for clarification if the hint is unclear or ambiguous
- Identify any debug code, temporary changes, or unrelated modifications that shouldn't be committed
Commit Strategy
- Apply the user's hint to determine grouping strategy, content focus, or message emphasis
- Group related changes into logical commits (e.g., separate documentation updates from code changes)
- Create focused commits that each serve a single purpose
- Prioritize commits in logical order (e.g., infrastructure before features)
- Use angular-style commit messages (feat:, fix:, docs:, refactor:, etc.)
- Focus commit messages on "why" not just "what"
- Include context about the change's purpose and impact
Execution
- For each logical group of changes:
- Add only specific files with
git add <specific-files> - Create commit with detailed angular-style message
- Verify the commit with
git show --stat
- Add only specific files with
- NEVER use
git add .- always be explicit about files - EXCLUDE debug code, temporary files, and unrelated changes
- ASK the user if they want to push changes after all commits are complete. The hint may suggest pushing, in which case you do not need to ask the user.
- If a PR exists for these changes, assume the PR title and/or body should be updated to reflect the new changes. Review the current state, and the changes just
Example Workflows
Default behavior:
- Commit 1:
docs: update memory management guidelines to clarify MCP usage - Commit 2:
feat: add intelligent commit slash command for better git workflow - Commit 3:
fix: correct memory.json file format documentation
With hint /scm-utils:commit each file separate:
- Commit 1:
docs: update commit.md to support optional hints - Commit 2:
docs: clarify memory management MCP tool differences - Commit 3:
feat: add new agent configuration file
With hint /scm-utils:commit only documentation:
- Commit 1:
docs: update commit workflow and memory management guidelines - (Skip non-documentation changes)
Related Skills
nsheaps/claude-code
tools
VerifiedTrustedCommunity
Reference material for Claude Code internals — the on-disk layout under ~/.claude and project-scope .claude, the plugin cache, session-env propagation, and the full hook lifecycle. Auto-recall when working on Claude-Code-related tasks: writing or debugging hooks, authoring plugins, inspecting session state, troubleshooting why an env var is or isn't visible to a Bash tool call, or when paths under ~/.claude or ~/.claude/plugins/ come up.
3SKILL.mdUpdated May 6, 2026
nsheaps/github-app-token
development
VerifiedTrustedCommunity
Manage GitHub App installation tokens in Claude Code sessions. Use when tokens expire, auth errors occur in long-running sessions, or when setting up GitHub App credentials for agent teams. <example>my github token expired</example> <example>refresh the github app token</example> <example>check token status</example> <example>set up github app authentication for this session</example>
3SKILL.mdUpdated Apr 22, 2026
nsheaps/auto-config
tools
VerifiedTrustedCommunity
Auto-detect project formatting tools and configure edit-utils settings
3SKILL.mdUpdated Apr 22, 2026
nsheaps/op
tools
VerifiedTrustedCommunity
Use this skill when the user asks about 1Password, secrets management, retrieving credentials, using op CLI, service accounts, secret references, vault operations, or any task involving the 1Password CLI (op). Also use when needing to inject secrets into environment variables, read passwords or API keys from 1Password, or manage 1Password items from the command line.
3SKILL.mdUpdated Apr 22, 2026