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

git-review

Guides git branching strategies, conventional commits, and pull request review workflows.

2|Updated Jun 8, 2026
Search Tags:#git#code review#pull request#conventional commits#merge conflict#monorepo#branching strategy
One-click install
npx skills add https://github.com/lunaticwithaduck/easytech3d --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/easytech3d/tree/main/.claude/skills/git-review
Command: npx skills add https://github.com/lunaticwithaduck/easytech3d --skill git-review-lunaticwithaduck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams struggle with inconsistent commit messages, unclear branching strategies, painful merge conflicts, and unstructured code reviews that let bugs slip through. This Skill provides decision frameworks, checklists, and command references to standardize git workflows and PR review processes. ## Core Features & Use Cases - Branching Strategy Selection: A decision tree comparing trunk-based development, GitHub Flow, Git Flow, and forking workflows based on team size and release cadence. - Conventional Commits & PR Templates: Ready-to-use commit message formats, PR templates, and reviewer/author checklists covering security, performance, and testing. - Git Command Reference: Practical commands for rebase, cherry-pick, bisect, stash, and merge conflict resolution, plus monorepo patterns with Turborepo and Nx. - Use Case: A team lead setting up a new repository can use this Skill to choose GitHub Flow, enforce conventional commits with commitlint and Husky hooks, and roll out a PR review checklist. ## Quick Start Ask the assistant to recommend a branching strategy and PR review checklist for a five-person team deploying continuously.

Frequently Asked Questions about git-review

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

FAQPage Schema
How do I choose a git branching strategy for my team?▼

Choose based on team size and release cadence: trunk-based development suits small teams with continuous deployment, GitHub Flow fits most teams with PR-based reviews, and Git Flow works for scheduled releases with compliance needs. GitHub Flow is the recommended default for most teams.

What is the conventional commits format?▼

Conventional commits use the format type(scope): description, with types like feat, fix, docs, refactor, perf, test, and chore. Breaking changes add an exclamation mark after the type or a BREAKING CHANGE footer, and the subject line stays under 72 characters in imperative mood.

How do I resolve git merge conflicts during a rebase?▼

Run git rebase origin/main, then open each conflicted file and edit the sections marked with conflict markers to keep the correct changes. Stage resolved files with git add and run git rebase --continue, or use git rebase --abort to start over.

What should a code review checklist include?▼

A review checklist should cover code quality, security issues like hardcoded secrets and injection risks, performance problems like N+1 queries, test coverage, and architecture concerns such as circular dependencies. Authors should keep PRs focused, self-review the diff, and include screenshots for UI changes.

Turborepo vs Nx for monorepo management?▼

Turborepo fits the Next.js and Vercel ecosystem with simple setup and a pipeline-based turbo.json configuration. Nx suits larger monorepos needing a plugin ecosystem and advanced caching, while pnpm workspaces handle dependency management without build orchestration.

When should I avoid force-pushing git branches?▼

Only force-push branches that you own exclusively, such as your own feature branches after a rebase. Never force-push shared branches like main or develop, since rewriting public history causes teammates to lose work and breaks their local clones.

Related Skills

Explore More Software Engineering Skills→
kagentikagenti
292

orchestrate:security

Create and audit security governance files like CODEOWNERS and SECURITY.md.

Official
Intermediate
Sir-chawakornSir-chawakorn
33

changelog-generator

Generate changelogs from Git commits in Markdown format.

Community
Intermediate
tarekBassiounytarekBassiouny

Najaah LMS - Code Quality Agent

Enforces code quality standards for the Najaah LMS project using Pest, PHPStan, and Laravel Pint.

Community
Advanced
wahidyankfwahidyankf
3

repo-practicing-trunk-based-development

Enforce small, frequent commits to the main branch for Trunk Based Development workflows.

Community
Advanced