技能 git-pr-workflows-git-workflow
📦

git-pr-workflows-git-workflow

安全 ⚙️ 外部命令

Automate Git PR workflows with multi-agent orchestration

Streamline your git workflow from code review to pull request creation. This skill coordinates specialized AI agents to ensure code quality, run tests, generate conventional commits, and create well-documented PRs.

支援: Claude Codex Code(CC)
🥉 74 青銅
1

下載技能 ZIP

2

在 Claude 中上傳

前往 設定 → 功能 → 技能 → 上傳技能

3

開啟並開始使用

測試它

正在使用「git-pr-workflows-git-workflow」。 Code review for a new authentication feature with 5 modified files

預期結果:

Code Review Report: 2 high-severity issues (missing input validation on login endpoint, hardcoded credentials in config), 3 medium issues (inconsistent error handling, missing logging), 5 low issues (style violations). Recommendations include implementing rate limiting and using environment variables for secrets.

正在使用「git-pr-workflows-git-workflow」。 Test execution for API endpoint changes

預期結果:

Test Results: 47 passed, 2 failed (integration tests for new endpoint), 0 skipped. Coverage: 84% statements, 78% branches, 81% functions. Untested critical paths: error handling in auth middleware, edge cases for token expiration.

安全審計

安全
v1 • 2/25/2026

All static analysis findings are false positives. The scanned file (SKILL.md) is a markdown documentation file, not executable code. Detected patterns like backticks are markdown formatting for code examples, and terms flagged as cryptographic references are ordinary text mentions (e.g., feature flags). No actual security risks exist in this developer productivity skill.

1
已掃描檔案
143
分析行數
1
發現項
1
審計總數

風險因素

⚙️ 外部命令 (10)
SKILL.md:29 SKILL.md:36 SKILL.md:37 SKILL.md:38 SKILL.md:39 SKILL.md:40 SKILL.md:41 SKILL.md:42 SKILL.md:129 SKILL.md:138
審計者: claude

品質評分

38
架構
100
可維護性
87
內容
50
社群
100
安全
91
規範符合性

你能建構什麼

Enterprise Development Teams

Standardize git workflows across large teams with consistent code review, testing, and PR creation processes that follow Conventional Commits and branch protection policies.

Solo Developers

Automate repetitive git tasks and ensure code quality through multi-agent review before committing, reducing bugs and maintaining professional standards.

Open Source Maintainers

Streamline contribution workflows with automated PR descriptions, reviewer assignments, and structured commit messages that improve project maintainability.

試試這些提示

Basic Code Review 
Review my uncommitted changes for code quality issues. Check for style violations, security vulnerabilities, and missing error handling. Generate a report with severity levels.
Test Coverage Analysis 
Execute all test suites for my modified code. Run unit, integration, and e2e tests. Generate a coverage report and identify untested code paths that need attention.
Conventional Commit Generation 
Analyze my changes and create Conventional Commits format messages. Categorize changes (feat/fix/docs/etc.), write clear subject lines under 50 characters, and include detailed bodies explaining what and why.
Full PR Workflow 
Orchestrate the complete git workflow: review code quality, run tests, generate commit messages, prepare branch strategy, and create a comprehensive PR description with testing summary and deployment notes.

最佳實務

  • Commit early and often with atomic commits that represent single logical changes
  • Follow Conventional Commits specification for consistent, parseable commit messages
  • Keep pull requests under 400 lines to enable effective code review

避免

  • Skipping tests with --skip-tests flag except in emergency scenarios
  • Creating large PRs with multiple unrelated changes that are difficult to review
  • Merging without addressing critical or high-severity code review findings

常見問題

What AI agents does this workflow use?
The workflow coordinates specialized agents: code-reviewer for quality analysis, test-automator for test execution, prompt-engineer for commit message generation, docs-architect for PR descriptions, and deployment-engineer for branch management and pre-push validation.
Can I use this with trunk-based development?
Yes, the workflow supports both trunk-based and feature-branch strategies. Use the --trunk-based flag for direct-to-main workflow with feature flags, or --feature-branch (default) for isolated branch development.
What is Conventional Commits format?
Conventional Commits is a specification for commit messages with format: type(scope): subject. Types include feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert. This enables automated changelog generation and semantic versioning.
Does this skill execute git commands automatically?
No, this skill provides workflow guidance, instructions, and generates artifacts like commit messages and PR descriptions. You must manually execute the git commands or integrate with automation tools.
How do I handle breaking changes?
The workflow includes breaking change analysis in Phase 1. If breaking changes are detected, they will be documented in commit footers with BREAKING CHANGE: prefix and included in the PR description with migration notes.
Can I customize the review criteria?
Yes, the code review prompts can be customized to focus on specific quality attributes, security concerns, or performance requirements relevant to your project. Modify the prompts in Phase 1 to match your standards.

開發者詳情

作者

sickn33

授權

MIT

儲存庫

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/git-pr-workflows-git-workflow

引用

main

檔案結構

📄 SKILL.md