Stats
Actions
Tags
From pro-workflow
Runs quality gates, reviews staged changes for issues, and creates a conventional commit. Useful when ready to commit after making changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pro-workflow:smart-commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use when saying "commit", "save changes", or ready to commit after making changes.
Use when saying "commit", "save changes", or ready to commit after making changes.
git status
git diff --stat
npm run lint 2>&1 | tail -5
npm run typecheck 2>&1 | tail -5
npm test -- --changed --passWithNoTests 2>&1 | tail -10
git add <specific files>
git commit -m "<type>(<scope>): <summary>"
Before committing, check staged changes in production code (not test files) for:
console.log / debugger statements (suppressed in test files — see Review Suppressions)TODO(JIRA-123) is fine)Flag any issues before proceeding.
<type>(<scope>): <short summary>
<body - what changed and why>
Types: feat, fix, refactor, test, docs, chore, perf, ci, style
git add -A or git add ..Do NOT flag these during the pre-commit scan. They add noise without catching real bugs:
console.log in test filesnpx claudepluginhub rohitg00/pro-workflow --plugin pro-workflowGuides systematic git commits: checks staging status, reviews diffs, splits changes into atomic commits, formats conventional messages. Use before PRs or when committing code.
Creates Conventional Commits with pre-commit checklists for scope, quality, tests, linting, formatting, and documentation. Ensures one logical change per commit before git commit.
Generates conventional git commit messages with automatic type/scope detection from file changes/diffs, runs pre-commit validation for secrets/debug code/large files, stages changes, and executes commit.