AgentSkillsCN

commit-push-pr

全流程：秘密扫描、提交、推送，并创建 Pull Request（GitHub + Azure DevOps）

SKILL.md
--- frontmatter
name: commit-push-pr
description: "Full cycle: secret scan, commit, push, and create PR (GitHub + Azure DevOps)"
disable-model-invocation: true

Context

Complete git cycle in one skill: scan for secrets, stage and commit changes, push to remote, and create a pull request. Supports both GitHub and Azure DevOps.

Reference: .claude/skills/utils/platform-detection.md for platform detection logic. Reference: .claude/skills/utils/git-helpers.md for git operations.

Inputs

$ARGUMENTS - Optional: target branch for the PR (defaults to default branch: main/master)

Steps

1. Detect Platform

Follow platform detection steps from .claude/skills/utils/platform-detection.md.

2. Analyze and Stage Changes

  • •Run git status to see modified/untracked files
  • •Run git diff and git diff --cached to understand changes
  • •Identify logically related changes that form one atomic commit
  • •NEVER stage: .env, *.key, *.pem, credentials.*, *secret* files
  • •Stage with specific git add <file> commands (not git add -A)

3. 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.

4. Generate Conventional Commit

  • •Run git log --oneline -5 to match recent commit style
  • •Follow Conventional Commits: <type>[scope]: <description>
  • •Types: feat, fix, docs, style, refactor, test, chore, ci
  • •Keep under 72 characters, imperative mood
  • •Extract work item references from branch name if present:
    • •GitHub: Closes #123 or Fixes #123
    • •Azure DevOps: AB#456

5. Commit

Create the commit with the generated message.

6. Push

  • •Determine current branch: git branch --show-current
  • •Push with tracking: git push -u origin <branch>

Pre-push Hook: If the pre-push hook is installed (via --install-tools), it will automatically run a vulnerability check before pushing:

  • •CRITICAL vulnerabilities: Push is blocked - fix before pushing
  • •HIGH vulnerabilities: Warning shown but push allowed
  • •Bypass: git push --no-verify (not recommended)

7. Create Pull Request

Determine target branch:

  • •If $ARGUMENTS specifies a branch, use that
  • •Otherwise, detect default branch: git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'
  • •Fall back to main

Generate PR content:

  • •Title: Short, derived from branch name and commits (under 70 chars)
  • •Body: Summary of changes, testing checklist, linked items

GitHub:

bash
gh pr create --title "<title>" --body "<body>" --base <target>

Azure DevOps:

bash
az repos pr create --title "<title>" --description "<body>" --target-branch <target> [--work-items <id>]

8. Report

code
## Commit + PR Report

**Commit:** `<hash>` - <message>
**Branch:** <branch> → <target>
**PR:** <url>
**Changes:** X files changed
**Linked items:** #123 / AB#456 (if any)

Verification

  • •No secrets in staged changes (enforced by pre-commit hook)
  • •Commit message follows conventional format
  • •Branch is pushed to remote (pre-push vulnerability check passed)
  • •PR is created and accessible
  • •Work items/issues linked (if detected)
  • •No CRITICAL vulnerabilities in dependencies (if pre-push hook installed)