git-pr-workflows-git-workflow

Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g

Author

Install

Hot:1

Download and extract to your skills directory

Copy command and send to OpenClaw for auto-install:

Download and install this skill https://openskills.cc/api/download?slug=sickn33-skills-git-pr-workflows-git-workflow&locale=en&source=copy

Git PR Workflow - Multi-Agent Automation Orchestration

Skill Overview


By coordinating multiple specialized intelligent agents, this workflow automates the entire Git process—from code review to PR creation—ensuring code quality, test coverage, and compliance with commit conventions.

Use Cases


  • Code Quality Management for Development Teams: Suitable for teams that need standardized commit rules, automated code review, and automated testing, preventing low-quality code from entering the main branch.

  • Enhancing CI/CD Pipelines: Add intelligent code review and PR automation to existing CI/CD pipelines to improve the reliability of deployment-ready checks.

  • Boosting Productivity for Individual Developers: Individual developers can use this workflow to automatically generate compliant commit messages and PR descriptions, reducing manual writing time.
  • Core Features


  • Five-Stage Automated Review: Covers the complete flow, including pre-commit code review, dependency change analysis, test validation, commit message generation, and PR metadata configuration.

  • Support for Multiple Branch Strategies: Supports two workflows—Feature Branch (default) and Trunk-Based. Merge strategies and branch naming conventions can be configured.

  • Flexible Configuration Options: Offers flags such as --skip-tests, --draft-pr, --squash, --conventional, etc., to adapt to different team collaboration needs.
  • Frequently Asked Questions

    What Git branching strategies does this workflow support?


    It supports two strategies: Feature Branch (feature branches) and Trunk-Based (mainline development). Feature Branch is the default mode and works well for teams that need isolated development and review. Trunk-Based is suitable for teams that want frequent commits to the main branch, and it can be used alongside feature flags.

    How can I skip the automated testing step?


    Use the --skip-tests flag to bypass automated test execution. This is only recommended for specific scenarios (e.g., documentation-only changes), because skipping tests can introduce code quality risks.

    Can I configure custom code review rules?


    The workflow performs reviews using multiple specialized agents, such as code-reviewer, test-automator, deployment-engineer, and more. You can customize review rules and check items by modifying the Prompts in each stage.