commit-work
Commit work
Goal
Make commits that are easy to review and safe to ship:
- only intended changes are included
- commits are logically scoped (split when needed)
- commit messages describe what changed and why
Inputs to ask for (if missing)
- Single commit or multiple commits? Default to multiple small commits when there are unrelated changes.
- Any extra rules: max subject length, required scopes.
Workflow
More from soyio-id/skills
create-pr
Create a clear, review-ready pull request with gh CLI. Gather context from commits and diff, follow repository templates, push safely, and return the PR URL with merge guidance.
10using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
9create-worktree
Create an isolated worktree for a new branch, existing branch, or PR review. Prefer repo-local worktree commands when they exist, and fall back to vanilla git worktrees otherwise.
8prepare-security-prs
Triage and prepare automated dependency security PRs for merge with minimal risk. Identify bot PRs that need intervention, resolve required issues only, refresh stale branches safely, detect superseded PRs, and keep diffs dependency-focused.
8fix-vulnerabilities
Fix multiple dependency vulnerabilities across multiple repos. Parses Vanta-style vulnerability entries, groups by repo, creates a single fix branch per repo, applies all fixes, verifies compatibility, and creates PRs after user approval. Use when the user says '/fix-vulnerabilities' or asks to fix vulnerabilities across repos.
7create-production-pr
Create a production promotion PR from main/master to production in an allowed repo or the current repo. Use the repo PR template when available, list included PRs, and generate a date-based title with production-only version suffixes.
6