スキル 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