skills.rest
lunaticwithaduck
lunaticwithaduckCOMMUNITY
Explore all skills by this author →
GitHub

git-review

Guide branching models, PR review processes, and commit conventions for team workflows.

Updated Aug 23, 2026
Search Tags:#git#workflow#branching#monorepo#review#pull-request#conventional-commits
One-click install
npx skills add https://github.com/lunaticwithaduck/majstorbg --skill git-review-lunaticwithaduck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-review
Source: https://github.com/lunaticwithaduck/majstorbg/tree/main/packages/.claude/skills/git-review
Command: npx skills add https://github.com/lunaticwithaduck/majstorbg --skill git-review-lunaticwithaduck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review and Git workflow inconsistencies waste time, degrade quality, and cause misaligned branches.

Core Features & Use Cases

  • Branching strategy guidance (Git Flow, trunk-based, GitHub Flow) for different team sizes
  • PR review best practices, checklists, and conflict resolution patterns
  • Conventional commits, semantic versioning guidance, and PR templates for consistent messaging
  • Monorepo handling guidance and tooling recommendations

Quick Start

Review a sample pull request and apply the GitHub Flow branching model to a small feature.

Frequently Asked Questions about git-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best git branching model for a monorepo with a large team?▼

For large monorepo teams, git workflow guidance recommends adopting trunk-based development or Git Flow to manage branching models, ensure consistent PR review processes, and handle complex merges effectively.

How do I enforce conventional commits in our pull request workflow?▼

You can enforce conventional commits in your pull request workflow by applying PR templates, semantic versioning guidance, and PR review checklists to standardize commit messaging and review processes across your team.

Does this code review guidance work for open source projects?▼

Yes, the code review guidance applies to open source projects, scaling from small to large teams by providing best practices, conflict resolution patterns, and branching models like GitHub Flow for distributed collaboration.

How do I resolve git merge conflicts consistently during PR reviews?▼

To resolve git merge conflicts consistently during PR reviews, apply a reproducible conflict-resolution workflow that standardizes branching models and integrates with PR review checklists for team collaboration.

What's the difference between Git Flow and GitHub Flow for small features?▼

Git Flow uses distinct release and develop branches for complex releases, while GitHub Flow uses a simpler trunk-based branching model directly off main, making it ideal for small features and continuous deployment.

Related Skills

Explore More Software Engineering Skills→
cbown75cbown75

git-conventions

Enforce conventional commit formatting and branch hygiene across repositories.

Community
Advanced
Sumeet138Sumeet138
1

changelog-automation

Generate release notes and changelogs from commits and PRs.

Community
Advanced
netresearchnetresearch
51

git-workflow

Standardize Git branching, commit conventions, and PR workflows across teams.

Official
Advanced
mdmagnuson-creatormdmagnuson-creator

merge-conflicts

Merge target branches into source branches and resolve pull request conflicts.

Community
Advanced