b2c-ios-pre-pr-review

Summarize all Git branch changes before opening a pull request.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/herren-official/product-agents --skill b2c-ios-pre-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b2c-ios-pre-pr-review
Source: https://github.com/herren-official/product-agents/tree/main/skills/b2c-iOS/pre-pr-review
Command: npx skills add https://github.com/herren-official/product-agents --skill b2c-ios-pre-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

브랜치의 변경사항을 한눈에 파악하고, 변경 파일과 영향 범위를 자동으로 요약하여 PR 리뷰를 간소화합니다.

Core Features & Use Cases

  • 자동 변경사항 집계: 현재 브랜치의 차이점 파일 리스트와 변경 요약을 생성합니다.
  • 다중 레이어 리뷰: 코드, 구성, 문서 변경사항을 한 번에 검토할 수 있습니다.
  • Use Case: 대규모 PR에서 변경 내용을 빠르게 파악하고 리뷰 커뮤니케이션을 개선합니다.

Quick Start

Run this skill on your current branch to generate a concise summary of all changes before creating the PR.

Frequently Asked Questions about b2c-ios-pre-pr-review

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

FAQPage Schema
How do I summarize Git branch changes before creating a pull request?

To summarize Git branch changes before creating a pull request, run this skill on your current branch. It automatically collects file diffs and generates a concise summary of code, configuration, and documentation modifications for reviewers.

What is a pre-PR review workflow for iOS projects?

A pre-PR review workflow for iOS projects aggregates all branch changes into a structured summary before opening a pull request. It enables reviewers to quickly understand diffs across code, configuration, and documentation files.

How do I automatically collect diffs for a large PR code review?

You can automatically collect diffs for a large PR code review by triggering this skill on your current Git branch. It generates a structured review guidance summary that simplifies identifying changed files and their impact scope.

Can I review code, configuration, and documentation changes together before opening a PR?

Yes, you can review code, configuration, and documentation changes together before opening a PR. This skill provides multi-layer review capabilities that aggregate all file differences from your current branch into one summary.

Does this pre-PR review skill work with any Git branch?

Yes, this pre-PR review skill works with any active Git branch. It automatically detects and collects the branch differences to generate a contextual summary of all modifications before you create a pull request.

What are the limitations of automated diff collection for PR reviews?

Automated diff collection for PR reviews focuses on summarizing file changes and impact scope, but it does not replace manual verification of logic. It simplifies communication for large PRs but reviewers still need to validate the actual code implementation.