Execute the EaseUI commit workflow end-to-end with branch safety, tests, changelog update, PM Hub sync, ByteRover deep sync, and push. Use when the user asks to commit, says Copu or Now, or requests commit message generation and git push.
Use this skill whenever a user asks to commit code, generate a commit message, says Copu, or says Now (changelog-first).
Create a safe, high-quality, conventional commit that includes:
If user says
Now: Run Step 3 (Changelog) first, then continue from Step 0.
Always execute this sequence exactly: 0. Branch safety
git branch --show-current
main or master, create/switch to a feature branch unless user explicitly asks to commit to main.main or master.brv query "<what was changed and why>"
cd app && npx jest --passWithNoTests
Do not commit with known failing tests.
Edit app/src/app/changelog/page.tsx:
0.01Month D, YYYY)labelTypenew, improved, or fixCheck and update only if affected: README.md, docs/*, roadmap docs.
Security scan:
git diff --cached | grep -iE "(api[_-]?key|token|password|secret|credential)"
If secrets found: STOP, warn user.
Split decision: Split commits if different types mixed (feat + fix), multiple scopes, or FILES > 10 unrelated.
Commit format:
<type>(<scope>): <Subject>
<Body explaining what and why>
<Footer>
Types: feat, fix, ref, perf, docs, test, chore
Subject: imperative, capitalized, no period, max 70 chars.
Footer always includes:
Co-Authored-By: Claude <[email protected]>
Use heredoc for multi-line:
git commit -m "$(cat <<'EOF'
feat(scope): Subject line
Explain what changed and why.
Refs #123
Co-Authored-By: Claude <[email protected]>
EOF
)"