Run quality gates, review staged changes for issues, and create a well-crafted conventional commit. Use when saying "commit", "git commit", "save my 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 for:
console.log / debugger statementsFlag 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 ..