pr

Use when preparing changed work for a pull request. Inspect git status and diff, keep unrelated work out, summarize the change, gather verification evidence, and draft a concise PR title and body.

Jump to install

Repository: yansfil/inflearn-cagongmap
Last source activity: July 9, 2026 at 07:26
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/yansfil/inflearn-cagongmap --skill pr

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

implement

Use when the user asks Claude Code to execute an approved PRD or scoped task. Read the requirements, create a live checklist, implement the smallest safe changes, and keep acceptance criteria and verification evidence tracked.

2026-07-30

verify

Use before declaring a task complete, after code/content/config changes, or when the user asks to verify, QA, smoke test, validate, or inspect whether something really works. Inspect the changed scope, run the right checks, verify runtime behavior when needed, and report evidence without inventing results.

2026-07-30

refactor

Use when the user asks for a codebase health check, structural cleanup, or refactor without a specific bug or feature in mind - phrases like "코드 정리해줘", "구조 점검해줘", "리팩토링 리포트 만들어줘", "정리하면 좋을 곳 점검해줘", "clean up this codebase", "refactor report", or "what's messy in here". Also use when the user wants to know whether dead code, duplicated logic, missing tests, or unused dependencies exist before deciding what to fix. This skill investigates and reports first, then only touches code the user has explicitly approved - it is not for feature work or bug fixes with a known target (use `implement` for those).

2026-07-30

View all from this repository

name	pr
description	Use when preparing changed work for a pull request. Inspect git status and diff, keep unrelated work out, summarize the change, gather verification evidence, and draft a concise PR title and body.
allowed-tools	["Bash","Read","Grep","Glob","Write","Edit"]

pr

Use this skill after implementation and verification, when the work needs to be reviewed or shipped through a pull request.

Workflow

Run git status --short.
Inspect the diff for the intended files.
Identify unrelated local changes and keep them out of the PR.
Confirm which verification commands or runtime checks actually ran.
Draft a short PR title.
Draft a PR body with summary, verification, and risks.
Commit or push only when the user explicitly asks.

Rules

Do not include unrelated worktree changes in a commit or PR.
Do not invent test results.
Put user-visible behavior before internal refactors.
Mention migrations, env changes, feature flags, data scripts, or manual setup.
If the branch is not ready, say what is missing instead of writing a polished PR body that implies completion.

PR Body Format

## Summary

- ...

## Verification

- ...

## Risk / Notes

- ...

pr

Source facts

Install options

Review the source files

More from this repository

More from this repository

pr

Workflow

Rules

PR Body Format

pr

Workflow

Rules

PR Body Format