# Orchestrate Git and Pull Request Workflows

Complex Git changes can reach review without consistent testing, commit structure, or deployment checks. This skill organizes review, validation, commits, branches, and pull request preparation.

## Install

```bash
npx skillstore add sickn33/git-pr-workflows-git-workflow
```

## Metadata

- Status: approved
- Slug: sickn33-git-pr-workflows-git-workflow
- Skillstore revision: r2
- Version status: missing
- Tree hash: a352d207d640587f8ece18b59d405dbb843fcdb61ae946acc208923552a79f94
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/git-pr-workflows-git-workflow
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/sickn33-git-pr-workflows-git-workflow
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-git-pr-workflows-git-workflow/manifest

## Capabilities

- Coordinates staged code review, dependency analysis, testing, commit planning, branch preparation, and pull request creation.
- Requests severity-ranked code review findings and breaking-change assessments from specialized agents.
- Plans unit, integration, and end-to-end test execution with coverage and gap analysis.
- Generates Conventional Commit messages and recommends atomic commit structure.
- Prepares branch strategies, pre-push checks, pull request descriptions, metadata, and reviewer checklists.
- Provides success criteria and rollback steps for changes after merge.

## Use Cases

- Prepare a Feature Pull Request: A software developer uses staged reviews, tests, commit guidance, and branch checks before opening a pull request.
- Standardize Repository Reviews: A repository maintainer applies consistent quality, security, compatibility, and reviewer checks across incoming changes.
- Assess Release Readiness: A release engineer combines test results, breaking-change analysis, branch policy, and rollback planning before merge.

## Prompt Templates

### Review Changes Before a Pull Request

```
Review my uncommitted changes for a pull request targeting [branch]. Identify quality issues, missing tests, and breaking changes. Do not modify files or push.
```

### Plan Conventional Commits

```
Prepare a Conventional Commit plan for [change summary]. Recommend atomic commits, scopes, subjects, and any breaking-change footer after reviewing the current diff.
```

### Run Staged Validation

```
Run the staged validation workflow for [target branch]. Review changes, execute available tests, report coverage gaps, verify branch readiness, and stop before remote actions.
```

### Prepare a Draft Pull Request

```
Prepare a draft pull request for [change]. Include review findings, test evidence, migration needs, deployment notes, rollback steps, labels, and reviewer recommendations. Request approval before any remote action.
```

## Limitations

- Depends on specialized agent types that may not exist in every host environment.
- References a detailed playbook that is not included in the published file set.
- Does not define executable automation, so agents must translate guidance into repository-specific commands.
- Cannot guarantee test coverage, branch protection, reviewer availability, or deployment readiness.

## Best Practices

- Confirm the target branch, repository policies, and remote action permissions before starting.
- Resolve critical and high-severity findings before creating commits or pull requests.
- Preserve test evidence, breaking-change notes, and rollback details in the pull request.

## Anti Patterns

- Do not skip tests without documenting the reason and residual risk.
- Do not push, rewrite history, enable auto-merge, or modify remote metadata without explicit approval.
- Do not claim coverage, CI readiness, or branch protection compliance without verified results.

## Security Audit

- Audited at: 2026-07-23T23:35:38.222\+00:00
- Summary: All 11 static findings are false positives caused by Markdown inline code around flags, a file path, a documented command, and a naming pattern. No prompt injection, reconnaissance, or executable Ruby or shell backtick behavior appears in SKILL.md. A medium-risk concern remains because the workflow can lead agents toward remote repository mutations without a mandatory confirmation gate.

## Stats

- Views: 111
- Downloads: 13
- Favorites: 0
- Popularity score: 0