AgentSkillsCN

save

自动添加所有更改，以生成的提交信息完成提交，并推送到 GitHub。快速的工作流程，助您轻松保存并同步所有工作成果。

SKILL.md
--- frontmatter
name: save
description: Automatically add all changes, commit with generated message, and push to GitHub. Quick workflow for saving and syncing all your work.
metadata:
  author: custom
  version: "1.0.0"
  argument-hint: [optional-commit-message]

Save and Push to GitHub

Automatically save all your changes and push them to GitHub with a single command.

How It Works

  1. •Check current repository status and changes
  2. •Analyze the changes to generate an appropriate commit message
  3. •Add all changes to staging
  4. •Create commit with generated (or provided) message
  5. •Push to remote repository

Workflow Steps

When /save is invoked:

  1. •

    Check Status: Run git status to see all untracked and modified files

  2. •

    Analyze Changes: Run git diff to understand what changed

  3. •

    Review Commit History: Run git log -5 --oneline to understand the project's commit message style

  4. •

    Generate Commit Message: Based on the diff analysis, create a concise commit message that:

    • •Summarizes the nature of changes (feature, fix, refactor, docs, etc.)
    • •Is concise (1-2 sentences)
    • •Follows the project's commit style
    • •If user provided an argument, use that as the commit message instead
  5. •

    Stage All Changes: Run git add . to stage all changes

  6. •

    Create Commit: Run `git commit -m "$(cat <<'EOF' [Generated or provided message]

    Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com EOF )"`

  7. •

    Push to Remote: Run git push to push changes to remote repository

  8. •

    Confirm Success: Run git status to verify everything was pushed successfully

Usage

bash
/save

Or with a custom commit message:

bash
/save "Add new feature for user authentication"

Important Notes

  • •All unstaged and untracked files will be added automatically
  • •A commit message will be generated based on the changes unless one is provided
  • •Changes will be pushed to the current branch
  • •If push fails (e.g., need to pull first), inform user and suggest next steps
  • •Never skip the Co-Authored-By tag

Error Handling

If any step fails:

  • •Inform the user clearly what went wrong
  • •Suggest corrective actions
  • •Don't proceed to next steps if a critical step fails