timtoronto634/commit-staged
.claude/skills/commit-staged/SKILL.md
Commit currently staged changes with a conventional commit message
tools
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add timtoronto634/timtoronto634.github.io commit-stagedInstall 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 16, 2026, 2:36 PM12.6s1 file scanned
SKILL.md
- name:
- commit-staged
- description:
- Commit currently staged changes with a conventional commit message
- allowed-tools:
- Bash(git *)
Commit the currently staged changes following these steps:
- Check the current branch name. If on
mainormaster, create a new branch with a descriptive name based on the staged changes (e.g.,feat/add-login-page) and switch to it before committing - Run
git statusto see staged changes - Run
git diff --cachedto review what will be committed - Run
git log --oneline -5to see recent commit message style - If there are no staged changes, inform the user and stop
- Draft a concise commit message following Conventional Commits style (e.g.,
feat:,fix:,docs:,build:,chore:) - Create the commit using a HEREDOC for the message, appending:
Co-Authored-By: Claude Opus 4.6 <[email protected]> - Run
git statusto confirm the commit succeeded
Related Skills
timtoronto634/merge-pr
tools
VerifiedTrustedCommunity
Merge a GitHub pull request by number using squash merge
SKILL.mdUpdated Apr 16, 2026
timtoronto634/create-pr
testing
VerifiedTrustedCommunity
Create a GitHub pull request from the current branch with a summary and test plan
SKILL.mdUpdated Apr 16, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026