Git Push

Git Push

用于在用户明确要求时，一次性完成 pull -> commit -> push。

Workflow

1. Pull first

• Run git pull.
• If merge conflict occurs, stop immediately and report conflicted files.
• If pull fails for other reasons, stop and report the error.

2. Analyze changes

• Check git status and git diff HEAD.
• If there is no change to commit, stop and report no-op.

3. Create commit message

• Follow commit type rules from commitlint.config.cjs:
  • feat, fix, update, refactor, style, doc, test, framework, revert
• Format:
  • First line: Type: summary
  • Blank line
  • Bullet list of key changes
• Do not add auto-generated byline text.

4. Commit and push

• Stage changes with git add ..
• Create commit.
• Push to remote branch.

5. Report result

• Return commit hash, commit message summary, branch name, and push status.

Safety constraints

• Only run this skill when user explicitly asks to commit/push.
• If commitlint fails, adjust message and retry once.
• Do not run destructive git commands.

Source: jerrywu001/vue3-toastify — distributed by TomeVault.