Stats
Actions
Tags
From dev-workflow
Create a git commit following Conventional Commits. Use when the user says "commit", "commit these changes", has finished a logical unit of work, or wants to save progress to git. Analyzes the staged diff to infer type/scope, scans for secrets and sensitive files, warns before committing to main/master, and never bypasses hooks without permission.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-workflow:commitsonnetThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Automate git commits with Conventional Commits format and security validation.
Automate git commits with Conventional Commits format and security validation.
Shared rules (pre-commit analysis, staged validation, Conventional Commits format + type table, scope detection, security scan, error handling) live in ../../shared/commit-basics.md. Read that file at the start of the run and follow it.
/commit — Interactive mode (analyze changes, suggest message)/commit "feat: add feature" — Direct commit/commit "feat(scope): description" — With scopegit rev-parse --git-dir.git/MERGE_HEAD and .git/rebase-merge must not existmain/master? Warn before committingFollow shared/commit-basics.md → Pre-commit Analysis and Validate Staged Changes.
If not provided as argument:
shared/commit-basics.mdshared/commit-basics.md → Scope DetectionCommit using the HEREDOC pattern from shared/commit-basics.md → Commit Execution, then verify with git log -1 --oneline and git status.
See shared/commit-basics.md → Security and Error Handling.
If the project uses task IDs, detect one from the branch name (task/TASK-042), modified files, or the argument, and use it as the scope.
npx claudepluginhub jmlweb/skills-monorepo --plugin dev-workflowGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.