practical-stack · p-iknow · Oct 25, 2025 · Oct 25, 2025 · Oct 25, 2025 · Oct 25, 2025
diff --git a/.claude/commands/make-branch.md → .claude/commands/branch.md b/.claude/commands/make-branch.md → .claude/commands/branch.md
@@ -5,14 +5,14 @@ allowed-tools:
   - Bash(git checkout:*)
 ---
 
-# make-branch
+# branch
 
 Generate consistent branch names from GitHub issue information.
 
 ## Usage
 
 ```
-/make-branch [<type>]: <description>
+/branch [<type>]: <description>
 #<issue-index>
 ```
 
@@ -40,29 +40,29 @@ The description is intelligently shortened to keep the total branch name under 5
 
 ### Basic Examples
 
-- Input: `/make-branch [feat]: implement Button component
+- Input: `/branch [feat]: implement Button component
 #15`
 - Output: `i15-feat/implement-button-component`
 
-- Input: `/make-branch [fix]: resolve styling issues in Dialog
+- Input: `/branch [fix]: resolve styling issues in Dialog
 #23`
 - Output: `i23-fix/resolve-styling-issues`
 
-- Input: `/make-branch [doc]: add component usage examples
+- Input: `/branch [doc]: add component usage examples
 #42`
 - Output: `i42-doc/add-component-usage-examples`
 
 ### Shortening Examples
 
-- Input: `/make-branch [config]: issue template, pr template, claude commend
+- Input: `/branch [config]: issue template, pr template, claude commend
 #5`
 - Output: `i5-config/issue-pr-template`
 
-- Input: `/make-branch [agent]: rename custom commands to shorter aliases for easier invocation
+- Input: `/branch [agent]: rename custom commands to shorter aliases for easier invocation
 #21`
 - Output: `i21-agent/rename-commands-to-aliases`
 
-- Input: `/make-branch [agent]: update make-task-issue to use prompt-based input instead of editor
+- Input: `/branch [agent]: update issue-task to use prompt-based input instead of editor
 #19`
 - Output: `i19-agent/prompt-based-input`
 

diff --git a/.claude/commands/make-commit.md → .claude/commands/commit.md b/.claude/commands/make-commit.md → .claude/commands/commit.md
@@ -4,7 +4,7 @@ allowed-tools:
   - Bash
 ---
 
-# Smart Commit Command
+# Commit Command
 
 Analyze git changes (staged and unstaged) and create well-structured commits.
 

diff --git a/.claude/commands/make-task-issue.md → .claude/commands/issue-task.md b/.claude/commands/make-task-issue.md → .claude/commands/issue-task.md
@@ -8,19 +8,19 @@ allowed-tools:
   - Grep
 ---
 
-# Make Task Issue
+# Issue Task Command
 
 Create a new GitHub issue with comprehensive context gathering, requirement analysis, and solution design. This command guides you through a structured input process and enhances your input with AI-powered codebase analysis.
 
 ## Usage
 
 ```
-/make-task-issue [template-type]
+/issue-task [template-type]
 ```
 
 Or simply:
 ```
-/make-task-issue
+/issue-task
 ```
 
 **Note**: This command no longer accepts issue title as an argument. The title will be auto-generated based on your requirement input.
@@ -297,7 +297,7 @@ Add the issue to the repository's linked GitHub Project:
 
 ### Example 1: With template type specified
 ```bash
-/make-task-issue feat
+/issue-task feat
 ```
 
 This will:
@@ -311,7 +311,7 @@ This will:
 
 ### Example 2: Fully interactive
 ```bash
-/make-task-issue
+/issue-task
 ```
 
 This will:
@@ -371,10 +371,10 @@ The AI might then find your design system config, suggest how to integrate with
   * Uses `gh project item-add` to add issues to projects
   * Gracefully handles cases where no project is linked
 
-**Relationship with `/plan-issue`:**
-- `/make-task-issue` focuses on **problem definition**: gathering context, defining requirements, designing solutions
-- `/plan-issue` focuses on **implementation planning**: breaking down well-defined issues into actionable steps
-- Issues created with `/make-task-issue` are well-suited for `/plan-issue` to process
+**Relationship with `/plan`:**
+- `/issue-task` focuses on **problem definition**: gathering context, defining requirements, designing solutions
+- `/plan` focuses on **implementation planning**: breaking down well-defined issues into actionable steps
+- Issues created with `/issue-task` are well-suited for `/plan` to process
 
 ## Error Handling
 

diff --git a/.claude/commands/make-command.md b/.claude/commands/make-command.md
@@ -649,5 +649,5 @@ Generated file: `.claude/commands/test-api.md`
 ## Reference
 
 - Official guide: https://docs.claude.com/en/docs/claude-code/slash-commands
-- Existing commands: [make-branch.md](/.claude/commands/make-branch.md), [make-commit.md](/.claude/commands/make-commit.md), [make-pr.md](/.claude/commands/make-pr.md), [make-task-issue.md](/.claude/commands/make-task-issue.md), [plan-issue.md](/.claude/commands/plan-issue.md)
+- Existing commands: [branch.md](/.claude/commands/branch.md), [commit.md](/.claude/commands/commit.md), [pr.md](/.claude/commands/pr.md), [issue-task.md](/.claude/commands/issue-task.md), [plan.md](/.claude/commands/plan.md)
 - Frontmatter fields: description (required), argument-hint, allowed-tools, model, disable-model-invocation
diff --git a/.claude/commands/plan-issue.md → .claude/commands/plan.md b/.claude/commands/plan-issue.md → .claude/commands/plan.md
@@ -8,16 +8,16 @@ allowed-tools:
   - Grep
 ---
 
-# Plan Issue
+# Plan Command
 
 Fetch a well-structured GitHub issue and create an interactive, detailed implementation plan with clear rationale for each decision.
 
-**Note**: This command works best with issues created using `/make-task-issue`, which provides structured Context, Requirement, and Solution sections. This command focuses on breaking down the problem into actionable implementation steps, not on defining the problem itself.
+**Note**: This command works best with issues created using `/issue-task`, which provides structured Context, Requirement, and Solution sections. This command focuses on breaking down the problem into actionable implementation steps, not on defining the problem itself.
 
 ## Usage
 
 ```
-/plan-issue <issue-number> [--no-review]
+/plan <issue-number> [--no-review]
 ```
 
 **Required argument:**
@@ -49,7 +49,7 @@ Extract and analyze:
 ### 3. Analyze Issue Content
 
 **Expected Issue Structure:**
-Issues created with `/make-task-issue` will have the following sections:
+Issues created with `/issue-task` will have the following sections:
 - **Context**: Background and why this is needed
 - **Requirement**: What needs to be done and expected outcome
 - **Solution**: Proposed approach (may be empty or brief)
@@ -75,7 +75,7 @@ Issues created with `/make-task-issue` will have the following sections:
 Create a structured implementation plan with the following sections:
 
 **IMPORTANT - Separation of Concerns:**
-- The issue already contains Context, Requirement, and Solution (from `/make-task-issue`)
+- The issue already contains Context, Requirement, and Solution (from `/issue-task`)
 - **DO NOT re-do problem definition work** - use what's already in the issue
 - **FOCUS ON** breaking down the solution into actionable implementation steps
 - Your job is to create a concrete execution plan, not to redefine the problem
@@ -166,7 +166,7 @@ Once the user approves the plan:
 ### Basic Usage (with interactive review)
 
 ```bash
-/plan-issue 13
+/plan 13
 ```
 
 This will:
@@ -180,7 +180,7 @@ This will:
 ### Quick Mode (skip review)
 
 ```bash
-/plan-issue 13 --no-review
+/plan 13 --no-review
 ```
 
 This will:
@@ -230,8 +230,8 @@ After analyzing the issue, the command will generate a plan like:
 - Think about testing requirements
 
 ### Separation of Concerns
-- **Problem definition** happens in `/make-task-issue` (Context, Requirement, Solution, Test Plan)
-- **Implementation planning** happens in `/plan-issue` (breaking down into steps)
+- **Problem definition** happens in `/issue-task` (Context, Requirement, Solution, Test Plan)
+- **Implementation planning** happens in `/plan` (breaking down into steps)
 - Don't waste time re-analyzing what's already well-defined in the issue
 - Focus your energy on creating a concrete, actionable execution plan
 

diff --git a/.claude/commands/make-pr.md → .claude/commands/pr.md b/.claude/commands/make-pr.md → .claude/commands/pr.md
@@ -5,14 +5,14 @@ allowed-tools:
   - Bash(git:*)
 ---
 
-# make-pr
+# pr
 
 Automatically generate draft pull requests with intelligent content analysis.
 
 ## Usage
 
 ```
-/make-pr
+/pr
 ```
 
 ## Purpose
@@ -104,10 +104,10 @@ Analyze `git diff` between current HEAD and base branch:
 
 ```bash
 # User runs command
-/make-pr
+/pr
 
 # System analyzes branch, commits, and code
 # Shows generated PR content for review
-# User approves/modifies content  
+# User approves/modifies content
 # Creates draft PR and opens in browser
 ```
diff --git a/docs/CONVENTIONAL_COMMITS.ko.md b/docs/CONVENTIONAL_COMMITS.ko.md
@@ -449,7 +449,7 @@ Implementation:
 
 다음 커스텀 명령어들이 자동으로 이 컨벤션을 강제합니다:
 
-### `/make-commit`
+### `/commit`
 
 **목적**: git 변경 사항을 분석하고 잘 구조화된 커밋 생성
 
@@ -458,9 +458,9 @@ Implementation:
 - "Requirement"와 "Implementation" 섹션이 있는 커밋 메시지 생성
 - 논리적 커밋을 보장하기 위해 파일을 의도별로 그룹화
 
-**참고**: [.claude/commands/make-commit.md](.claude/commands/make-commit.md)
+**참고**: [.claude/commands/commit.md](.claude/commands/commit.md)
 
-### `/make-branch`
+### `/branch`
 
 **목적**: GitHub 이슈 정보에서 일관된 브랜치 이름 생성
 
@@ -469,9 +469,9 @@ Implementation:
 - 형식으로 브랜치 이름 생성: `i{issue-number}-{type}/{description}`
 - 브랜치 이름이 최종 커밋과 일치하도록 보장
 
-**참고**: [.claude/commands/make-branch.md](.claude/commands/make-branch.md)
+**참고**: [.claude/commands/branch.md](.claude/commands/branch.md)
 
-### `/make-pr`
+### `/pr`
 
 **목적**: draft pull request 자동 생성
 
@@ -480,7 +480,7 @@ Implementation:
 - 올바른 타입 접두사로 PR 제목 생성
 - 커밋 분석을 기반으로 구조화된 PR 설명 생성
 
-**참고**: [.claude/commands/make-pr.md](.claude/commands/make-pr.md)
+**참고**: [.claude/commands/pr.md](.claude/commands/pr.md)
 
 ---
 

diff --git a/docs/CONVENTIONAL_COMMITS.md b/docs/CONVENTIONAL_COMMITS.md
@@ -449,7 +449,7 @@ We acknowledge the following gaps and areas for future improvement:
 
 The following custom commands automatically enforce these conventions:
 
-### `/make-commit`
+### `/commit`
 
 **Purpose**: Analyze git changes and create well-structured commits
 
@@ -458,9 +458,9 @@ The following custom commands automatically enforce these conventions:
 - Generates commit messages with "Requirement" and "Implementation" sections
 - Groups files by intent to ensure logical commits
 
-**Reference**: [.claude/commands/make-commit.md](.claude/commands/make-commit.md)
+**Reference**: [.claude/commands/commit.md](.claude/commands/commit.md)
 
-### `/make-branch`
+### `/branch`
 
 **Purpose**: Generate consistent branch names from GitHub issue information
 
@@ -469,9 +469,9 @@ The following custom commands automatically enforce these conventions:
 - Creates branch names in format: `i{issue-number}-{type}/{description}`
 - Ensures branch names align with eventual commits
 
-**Reference**: [.claude/commands/make-branch.md](.claude/commands/make-branch.md)
+**Reference**: [.claude/commands/branch.md](.claude/commands/branch.md)
 
-### `/make-pr`
+### `/pr`
 
 **Purpose**: Automatically generate draft pull requests
 
@@ -480,7 +480,7 @@ The following custom commands automatically enforce these conventions:
 - Generates PR titles with correct type prefixes
 - Creates structured PR descriptions based on commit analysis
 
-**Reference**: [.claude/commands/make-pr.md](.claude/commands/make-pr.md)
+**Reference**: [.claude/commands/pr.md](.claude/commands/pr.md)
 
 ---
-Original file line number
+Diff line change
@@ Expand Up / @@ -4,7 +4,7 @@ allowed-tools: @@
       - Bash
     ---
-    # Smart Commit Command
+    # Commit Command
     Analyze git changes (staged and unstaged) and create well-structured commits.
@@ Expand Down @@