κ°λ° κ³Όμ μμ μμ μ λ§₯λ½μ κΌΌκΌΌν λ΄μ μ»€λ° λ©μμ§μ Pull Request(PR)λ₯Ό λ¨κΈ°λ κ²μ΄, νλ μ μ§λ³΄μλ₯Ό μν΄ μΌλ§λ μ€μνμ§λ μ°λ¦¬ λͺ¨λ μ μκ³ μμ΅λλ€.
νμ§λ§ λ§μ κ°λ°μ λͺ°μ νλ€ λ³΄λ©΄ λ³κ²½ μ¬νμ κ±·μ‘μ μ μμ΄ μμ΄κΈ° λ§λ ¨μ΄κ³ , λ€λ¦κ² μ΄λ₯Ό λ Όλ¦¬μ μΈ λ¨μλ‘ μͺΌκ°μ΄ 컀λ°νλ μΌμ μ¬κ° λ²κ±°λ‘μ΄ κ² μλλλ€. μ μ±μ€λ½κ² PRμ μμ±νλ κ² λν μλΉν μλμ§κ° λλ μΌμ΄μ£ .
κ·Έλμ μ λ μ΄ λ°λ³΅μ μ΄κ³ μλͺ¨μ μΈ κ³Όμ μ LLMμ νμ©ν΄ μλνν΄λ³΄λ € ν©λλ€.
π custom slash command
claude code μλ custom slash command λΌλ κΈ°λ₯μ΄ μμ΅λλ€.
https://code.claude.com/docs/en/slash-commands#custom-slash-commands
Slash commands - Claude Code Docs
Control Claude's behavior during an interactive session with slash commands.
code.claude.com
.claude/commands λλ ν 리 μλμ μ°λ¦¬κ° μ¬μ©ν λͺ
λ Ήμ΄λ€μ μ€μ μ μ μν΄μ£ΌκΈ°λ§ νλ©΄ λ©λλ€.
μ΄λ² ν¬μ€νΈμμλ μμ λ΄μ©μ λΆμν΄ μ μ ν μ»€λ° λ©μμ§λ₯Ό μμ±νλ /commit λͺ λ Ήμ΄μ, νμ¬ λΈλμΉμ λ³κ²½ μ¬νμ μ’ ν©ν΄ Pull Request μ΄μμ μμ±ν΄μ£Όλ /pull-request λͺ λ Ήμ΄λ₯Ό μΆκ°ν΄λ³΄κ² μ΅λλ€.
π git commit λͺ λ Ήμ΄
commit μ νμκ³Ό μ μμ¬νλ±μ μμ μ§μΉ¨μΌλ‘ μ λ¬ν©λλ€.
---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
description: Create a git commit
---
## Context
- Current git status: !`git status`
- Current git diff (staged and unstaged changes): !`git diff HEAD`
- Current branch: !`git branch --show-current`
- Recent commits: !`git log --oneline --decorate`
## Your task
Analyze the changes in the working directory and create appropriate git commits.
**Important:**
1. Review all changed files (both staged and unstaged)
2. Group related changes together logically
3. If there are multiple unrelated changes, create separate commits for each logical group
4. Use only staged changes for commit
5. Avoid mixing unrelated changes in the same commit
6. Commit short summary and body must be in Korean (scope must be in English because it would be package name or directory name)
7. Do not co-author commits (Claude)
**Steps:**
- First, analyze the git status and diff to understand all changes
- Identify logical groups of related changes
- For each group:
- Create a commit with an appropriate message
- If changes are simple and related, a single commit is fine
Once you have staged the necessary changes for a commit group, create the commit.
Use the following format for the commit message:
```
(<scope>): <emoji type> <short summary>
<BLANK LINE>
<body (optional)>
<BLANK LINE>
```
emoji type can be one of the following:
- β¨ : add/fix feature
- βοΈ : comments or typo fix
- β»οΈ : refactor
- π¨ : add/change UI layout or CSS
- π± : add/change static files
- π¬ : apply code review
- π : documentation
- π : release commit
- π¦ : npm package update (package.json)
- β‘οΈ : improve performance
- π : fix bug
- π
: fix lint, prettier error
- π₯ : hot fix
- π§Ή : remove unnecessary code or files
- π· : add/change ci/cd workflow
- βοΈ : add/change project config file (eslintrc, prettierrc etc.)
- π¦ : commit changeset file
- π§ : work in progress, but commit for split large scale jobs
- π : fix rebase conflict issueπ μ¬μ© μμ
π pull request λͺ λ Ήμ΄
λμΌν λ°©μμΌλ‘ pull request λ₯Ό μμ±νλ λͺ λ Ήμ΄λ μΆκ°ν μ μμ΅λλ€.
pull request λ₯Ό μμ±νλ €λ©΄ GitHub μ μ κ·Όμ΄ κ°λ₯ν΄μΌνλλ°, GitHub MCP λ₯Ό μ¬μ©νμ§ μκ³ gh CLI λ‘ λ¨μνκ² μ²λ¦¬νλ λ°©μμ μ¬μ©νκ² μ΅λλ€.
μ¬μ©νλ €λ©΄ μ΅μ΄ μΈμ¦ κ³Όμ μ΄ νμν©λλ€.
https://cli.github.com/manual/gh_pr_create
GitHub CLI
Take GitHub to the command line
cli.github.com
μμ±ν pull request template md νμΌμ μμ±ν΄λκ³ , pull request description μμ± μμ μ΄λ₯Ό μ°Έκ³ νλλ‘ μ§μν©λλ€.
---
allowed-tools: Bash(git *), Bash(gh *), Bash(brew install gh)
description: Create a pull request
---
## Context
- Current git status: !`git status`
- Current branch: !`git branch --show-current`
- Recent commits on current branch: !`git log main..HEAD --oneline`
- Recent commit diffs on current branch: !`git log main..HEAD -p`
## Your task
Create a pull request for the current branch against the main branch on GitHub.
**Important:**
1. Ensure all changes are committed before creating the pull request
2. Use a clear and descriptive title for the pull request
3. Write a detailed description of the changes made in the pull request
4. Use Korean for the title and description. But `<scope>` in the title must be in English because it would be package name or directory name
**Steps:**
- First, ensure all prerequisites are met:
- If there are uncommitted changes, reject this task and ask user to commit first
- If the branch doesn't have an upstream configured, push the branch to the remote repository first
- Second, check all of the current branch commit ids ahead to target branch.
- Third, gather information about the changes made in the current branch
- Then, use the GitHub CLI to create a pull request with an appropriate title and description
- Use `gh` commands to create the pull request
- If `gh` is not installed, install it using `brew install gh`
- Use the `Pull Request Template Format` section below for the pull request title and description
- Create the pull request against the `main` branch
- Use `gh pr create --base main --title "<title>" --body "<description>"`
- Finally, provide the URL of the created pull request
**Pull Request Template Format:**
- Title: `(<scope>): <short summary>`
- Body: Use the format from `.github/PULL_REQUEST_TEMPLATE.md` file in the repository. Fill in the description section with a summary of changes, issues fixed, motivation, context, and any dependencies.
π μ¬μ© μμ
'π¨βπ» web.dev > ops' μΉ΄ν κ³ λ¦¬μ λ€λ₯Έ κΈ
| RSS ꡬλ μμ½ LLM Slack Bot λ§λ€κΈ° (0) | 2025.10.11 |
|---|---|
| GitHub Actions λ₯Ό νμ©ν release bot λ§λ€κΈ° (0) | 2023.04.24 |
| SVN μ μ΄μ©ν νμκ΄λ¦¬ PART.2 - SVN λΈλμΉ μ λ΅ μΈμ°κΈ° (1) | 2022.03.01 |
| SVN μ μ΄μ©ν νμκ΄λ¦¬ PART.1 - SVN μ΄λ? (0) | 2022.03.01 |
π¬ λκΈ