Gather git metadata and interview context to draft Korean PR descriptions.
npx skills add https://github.com/toongri/oh-my-toong-playground --skill make-pr-toongri
Please help me install this Agent Skill. Skill: make-pr Source: https://github.com/toongri/oh-my-toong-playground/tree/main/skills/make-pr Command: npx skills add https://github.com/toongri/oh-my-toong-playground --skill make-pr-toongri
The Claude Code workflow demands context-rich Korean PR descriptions, but manually fetching branch metadata, confirming the base, and conducting the necessary interview is cumbersome, so this skill orchestrates those steps before drafting the final narrative.
Ask the user about PR context using the clearance checklist and draft a Korean PR description that separates Changes from Review Points.
High-intent search queries and answers about installing and using this skill.
Writing a Korean PR description for Claude Code workflows involves gathering git metadata, confirming base branch synchronization, and conducting a structured interview to capture motivations and technical decisions. The output separates Changes and Review Points with verifiable checklist items.
The best way to structure PR review points and changes separately is to conduct a structured interview capturing technical decisions, then organize the output into Summary, Changes, Review Points, Checklist, and References sections for clear reviewer focus.
Yes, you need to sync your base branch before generating a PR summary. Rigorous base branch detection, synchronization, and conflict resolution keep the working branch aligned with the true merge target before any narrative is drafted.
Yes, you can automate fetching git metadata for conventional commit PR titles. When requested, the skill automatically gathers branch metadata, explores the repository, and drafts a Korean conventional-commit-title description separating Changes from Review Points.
An interview-based PR description process works by asking structured questions one at a time using a clearance checklist. It captures developer motivations, technical decisions, and reviewer concerns before drafting the final narrative.
A PR description for Korean software engineering review should include the thesis scope, separated Changes and Review Points, a verification checklist, and references. It requires confirming base branch freshness before delivering the final narrative.
kirvinFetch upstream changes and rebase the current Git branch onto them.
lvlup-swOrchestrate stacked GitHub pull requests with automated creation and merging.
gobikomAutomate git commits with natural language and conventional commit formatting.
masa-codehubAutomate GitHub pull request creation, rebasing, labeling, and review triggers.
