domains / families / software-engineering / git-pr-workflows-git-workflow

git-pr-workflows-git-workflow

combined

Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration. Orchestrate review, tests, commits, branch pushes, and pull-request creation with parallel agents. Use when completed changes must move through validation into a PR or guarded merge.

When to use

• Working on complete git workflow with multi-agent orchestration tasks or workflows
• Needing guidance, best practices, or checklists for complete git workflow with multi-agent orchestration
• Use for completed implementation work that must be reviewed, tested, committed, pushed to a topic branch, and opened as a pull request. Use the repository's dedicated maintainer or release workflow instead when one is mandatory.

When not to use

• The task is unrelated to complete git workflow with multi-agent orchestration
• You need a different domain or tool outside this scope
• This workflow cannot bypass branch protection, required reviews, repository permissions, or missing credentials.
• It does not authorize destructive cleanup, force pushes, merges, deployments, or releases beyond the user's request and repository policy.
• Keep unresolved environment or infrastructure failures explicit; do not convert them into source changes without evidence.

Skill page

Conflict

The two skills describe the same high-level goal (moving code from local changes to a PR) but diverge significantly in implementation strategy and safety constraints. The first skill (rmyndharis) is a 'multi-agent orchestration' template that relies on specific subagent types (code-reviewer, test-automator) and a rigid 3-phase pipeline with specific JSON output formats. It lacks safety gates regarding branch protection or repository policy. The second skill (sickn33) is a 'guarded' workflow that prioritizes repository policy (AGENTS.md), branch protection, and manual verification steps (git status, gh pr view) over automated subagent delegation. It explicitly forbids bypassing policy and includes a 'Policy Gate' phase that the first skill completely omits. Combining them is necessary to capture both the automated quality assurance steps (from skill 1) and the critical safety/policy compliance steps (from skill 2).