git-pr

To write a pull request title for a monorepo, use a standardized format like [Type(scope)]: Subject. Scopes help categorize changes across web, api, ai, infra, docs, or agent directories to clarify the modification area.

Generating a code review description that follows GitFlow conventions involves summarizing the change scope and highlighting key points concisely. This ensures reviewers understand the lightweight GitFlow strategy and branch context quickly.

Yes, you can automate PR formatting for specific contexts like AX-WMS by enforcing repository-specific review guidelines. This ensures titles and descriptions match the required Korean context and project standards automatically.

Creating a concise PR summary for reviewers in a Korean context requires emphasizing important changes and outlining the modification scope clearly. This approach reduces review time by providing straightforward Korean explanations.

Yes, the lightweight GitFlow strategy supports optional scopes including infra and agent. This allows monorepo structures to categorize pull requests effectively across diverse operational layers without rigid branching restrictions.

Your pull request title format may fail code review checks if it lacks the required [Type(scope)]: Subject structure. Enforcing naming conventions ensures compliance with review guidelines and maintains monorepo consistency.