Terminal
Terminal/Skill
Runs quality checks, reviews your staged changes for issues, and creates a well-written conventional commit.
By Rohit Ghumare
Works with
npx skills add rohitg00/pro-workflow --skill smart-commitUse 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 files