AgentSkillsCN

commit-push

暂存更改，以常规提交格式记录变更并进行秘密扫描，随后推送到远程仓库

SKILL.md
--- frontmatter
name: commit-push
description: Stage changes, create a conventional commit with secret scanning, and push to remote
disable-model-invocation: true

Context

Smart commit workflow that scans for secrets before staging, generates a conventional commit message based on the changes, commits, and pushes to the remote branch.

Inputs

$ARGUMENTS - Optional: specific files to commit, or commit message hint

Steps

1. Analyze Changes

  • •Run git status to see modified/untracked files
  • •Run git diff for unstaged changes and git diff --cached for staged changes
  • •Run git log --oneline -5 to see recent commit message style

2. Determine What to Stage

  • •If $ARGUMENTS specifies files, stage those files
  • •Otherwise, identify logically related changes that form one atomic commit
  • •NEVER stage: .env, *.key, *.pem, credentials.*, *secret* files
  • •Prefer specific git add <file> over git add -A

3. Stage Files

  • •Stage the identified files with git add <file>

4. Secret Scanning (handled by pre-commit hook)

Secret scanning is handled automatically by the git pre-commit hook (gitleaks). No manual scan step is needed here. If secrets are detected, the commit will be blocked.

5. Generate Commit Message

Follow Conventional Commits format:

code
<type>[optional scope]: <description>

Types: feat, fix, docs, style, refactor, test, chore, ci

Keep the description under 72 characters. Use imperative mood ("add" not "added").

6. Create Commit

  • •Create the commit with the generated message

7. Push to Remote

  • •Determine current branch: git branch --show-current
  • •Push with tracking: git push -u origin <branch>
  • •If push fails due to upstream changes, inform the user and suggest git pull --rebase

8. Verify

  • •Run git status to confirm state
  • •Run git log --oneline -1 to confirm the commit message
  • •Confirm push succeeded

Verification

  • •No secrets in the committed changes
  • •Commit message follows conventional format
  • •Only related changes are in the commit (atomic)
  • •Changes are pushed to remote