heikopanjas/commit-changes
commit-changes/SKILL.md
Commit specific staged changes to a git repository using conventional commits format. Use when the user asks to commit, stage, or check in particular files or changes.
development
Updated Apr 28, 2026
$ install --global
skillsauthnpx skillsauth add heikopanjas/agent-skills commit-changesInstall 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 28, 2026, 2:52 PM199.9s1 file scanned
SKILL.md
- name:
- commit-changes
- description:
- Commit specific staged changes to a git repository using conventional commits format. Use when the user asks to commit, stage, or check in particular files or changes.
- compatibility:
- Requires git
Skill: commit-changes
Commit specific changes to a git repository. Only the relevant modified files are staged — not all changes in the working tree.
For commit message guidelines, protocol, and examples, read the shared conventions:
shared/commit-conventions.md
Staging
Stage only the files relevant to the commit. Use git add <file>... rather than git add -A. If the user has not specified which files to include, inspect the working tree with git status and stage only the files that relate to the described change.
Related Skills
heikopanjas/update-changelog
testing
VerifiedTrustedCommunity
Record recent changes and decisions in the AGENTS.md file. Use when making project decisions, choosing technologies, establishing conventions, or completing significant changes that should be tracked in the project history.
SKILL.mdUpdated Apr 28, 2026
heikopanjas/swift-conventions
development
VerifiedTrustedCommunity
Swift coding conventions and best practices for modern Swift development. Use when writing, reviewing, or refactoring Swift code to ensure consistency with naming conventions, access control, async/await patterns, and SwiftUI/framework best practices.
SKILL.mdUpdated Apr 28, 2026
heikopanjas/semantic-versioning
development
VerifiedTrustedCommunity
Determine whether a version bump is required after code changes and apply semantic versioning (SemVer). Use when making code changes, fixing bugs, adding features, or introducing breaking changes to a project that uses SemVer.
SKILL.mdUpdated Apr 28, 2026
heikopanjas/rust-conventions
development
VerifiedTrustedCommunity
Rust coding conventions and best practices for idiomatic Rust development. Use when writing, reviewing, or refactoring Rust code to ensure consistency with error handling, RAII principles, naming conventions, and Rust edition best practices.
SKILL.mdUpdated Apr 28, 2026