Our review

Commits all current changes and pushes to the remote repository after automatic pre-push checks.

When to use it

Use this skill when the user asks to save progress, commit changes, or push to remote.

When not to use it

Do not use it if the user only wants to run checks without committing, or if untested changes need manual review.

name: cp description: Commit all current changes and push to the remote. Use when the user asks to commit, push, save progress, or ship changes. user_invocable: true

commit-and-push

Commit all current changes and push to the remote. All pre-push checks must pass before committing.

Run pre-push checks with auto-fix (quiet mode suppresses output on success):
```
tools/pre-push --fix -q
```
If this fails, fix the issues and re-run until it passes. Do NOT skip this step — it is the project's only gate against broken code.

Check for changes:

git status
git diff --stat
git log --oneline -5

Stage all changes (including any fixes from step 1):
```
git add -A
```
Write a commit message following the project convention:
- Prefix with synq: (lowercase)
- Concise summary line describing the "why"
- Add detail in the body for non-trivial changes

Commit using a HEREDOC:

git commit -m "$(cat <<'EOF'
synq: <summary>

<optional body>
EOF
)"