@yeongjaeyou/claude-code-config 0.19.0 → 0.21.0

package/.claude/agents/issue-resolver.md

@@ -33,8 +33,13 @@ gh issue view $ISSUE_NUMBER --json title,body,comments,milestone
 
 ### 3. Create Branch
 
+**Branch naming**: `{type}/{issue-number}-{short-description}`
+- `type`: From labels (`bug`->`fix`, `enhancement`->`feat`) or default `feat`
+- `short-description`: Slugified title (lowercase, hyphens, max 50 chars)
+
 ```bash
-git checkout -b issue-$ISSUE_NUMBER main
+# Example: fix/42-login-validation or feat/15-dark-mode
+git checkout -b $BRANCH_NAME main
 git submodule update --init --recursive
 ```
 

package/.claude/commands/gh/resolve-issue.md

@@ -6,6 +6,12 @@ description: Resolve GitHub Issue
 
 Act as an expert developer who systematically analyzes and resolves GitHub issues. Receive a GitHub issue number as argument and resolve the issue. Follow project guidelines in `@CLAUDE.md`.
 
+## Prerequisites
+
+Before starting the workflow:
+- **Serena MCP**: If not already active, run `activate_project` to enable semantic code analysis tools
+- **Clean state**: Ensure no uncommitted changes that could conflict with the new branch
+
 ## Workflow
 
 1. **Analyze Issue**:
@@ -24,7 +30,11 @@ Act as an expert developer who systematically analyzes and resolves GitHub issue
      4. If misaligned, ask user for clarification before proceeding
    - If no plan file, continue to next step
 
-3. **Create Branch**: Create and checkout a new branch named `issue-$ISSUE_NUMBER` from `main` or `master` branch.
+3. **Create Branch**: Create and checkout a new branch from `main` or `master` branch.
+   - **Branch naming convention**: `{type}/{issue-number}-{short-description}`
+     - `type`: Infer from issue labels (`bug` -> `fix`, `enhancement`/`feature` -> `feat`) or title prefix. Default to `feat` if unclear.
+     - `short-description`: Slugify issue title (lowercase, spaces to hyphens, max 50 chars, remove special chars)
+     - Examples: `fix/42-login-validation-error`, `feat/15-add-dark-mode`, `refactor/8-cleanup-auth`
    - **Initialize submodules**: When using worktree, run `git submodule update --init --recursive`
 
 4. **Update GitHub Project Status (Optional)**
@@ -40,18 +50,30 @@ Act as an expert developer who systematically analyzes and resolves GitHub issue
        ```
      - Skip if Status field does not exist
 
-5. **Analyze Codebase (MANDATORY)**: Before writing any code, spawn multiple Explorer agents in parallel to preserve main context:
+5. **Analyze Codebase (MANDATORY)**: Before writing any code, understand the affected areas:
+
+   **Tool Selection by Scope:**
+   | Scope | Approach |
+   |-------|----------|
+   | **Narrow** (1-2 files, specific function) | Serena: `get_symbols_overview` → `find_symbol` → `find_referencing_symbols` |
+   | **Broad** (multiple modules, architecture) | Explorer agents in parallel (preserves main context) |
+
+   **For broad changes**, spawn 2-3 Explorer agents simultaneously:
    - **Structure agent**: Overall architecture and file relationships
    - **Pattern agent**: Similar implementations in codebase
    - **Dependency agent**: Affected modules and consumers
 
-   ```
-   Task tool with subagent_type=Explore (launch 2-3 agents simultaneously)
-   ```
+   **For narrow changes**, use Serena directly:
+   1. `get_symbols_overview` on target file(s)
+   2. `find_symbol` with `include_body=True` for specific functions
+   3. `find_referencing_symbols` for impact analysis
 
 6. **Plan Resolution**: Based on analysis results, develop a concrete resolution plan and define work steps.
 
-7. **Resolve Issue**: Spawn sub-agents to modify code and implement features according to the plan.
+7. **Resolve Issue**: Implement the solution using appropriate tools:
+   - **Symbolic edits** (Serena): `replace_symbol_body`, `insert_after_symbol` for precise modifications
+   - **File edits**: For non-code files or complex multi-line changes
+   - **Sub-agents**: For large-scale parallel modifications
    - **If TDD enabled** (marker detected in Step 1):
      - **Reference**: See `feature-planner` skill for detailed TDD methodology
      1. 🔴 RED: Write failing tests first based on requirements

package/.claude/commands/tm/post-merge.md

@@ -111,7 +111,7 @@ Ask via AskUserQuestion about local branch deletion:
 
 ```bash
 # If deletion desired
-git branch -d <headRefName>  # e.g., issue-1
+git branch -d <headRefName>  # e.g., fix/1-login-bug
 ```
 
 ### 7. Check Next Task
@@ -171,7 +171,7 @@ TaskMaster Status:
 - Subtasks: all complete (1.1, 1.2, 1.3)
 
 Cleanup:
-- [x] Local branch deleted: issue-<N>
+- [x] Local branch deleted: {type}/<N>-{slug}
 - [x] TaskMaster status updated
 - [ ] CLAUDE.md updated (no changes)
 - [ ] AGENTS.md updated (no changes / not found)

package/.claude/commands/tm/resolve-issue.md

@@ -132,12 +132,13 @@ task-master show $TASK_ID
 ```bash
 # Create new branch from main or master
 git checkout main && git pull origin main
-git checkout -b issue-$ISSUE_NUMBER
+git checkout -b {type}/$ISSUE_NUMBER-{short-description}
 ```
 
-**Branch naming convention:**
-- `issue-1` (for GitHub Issue #1 work)
-- `issue-1-subtask-1.2` (for specific subtask only, optional)
+**Branch naming convention:** `{type}/{issue-number}-{short-description}`
+- `type`: From labels (`bug`->`fix`, `enhancement`->`feat`) or default `feat`
+- `short-description`: Slugified title (lowercase, hyphens, max 50 chars)
+- Examples: `fix/1-login-validation`, `feat/13-dark-mode`
 
 ### 5. Process Subtasks Sequentially
 
@@ -196,8 +197,8 @@ git commit -m "feat: [Task $TASK_ID] Task title
 Task Master reference: task $TASK_ID
 Closes #$ISSUE_NUMBER"
 
-# Push
-git push -u origin issue-$ISSUE_NUMBER
+# Push (use the branch name created in step 4)
+git push -u origin $BRANCH_NAME
 ```
 
 ### 8. Create PR

package/.claude/guidelines/id-reference.md

@@ -7,7 +7,7 @@ Reference for different ID formats used across GitHub and TaskMaster.
 | Type | Format | Example |
 |------|--------|---------|
 | PR/Issue number | `#N` | `#1`, `#13` |
-| Branch | `issue-N` | `issue-1`, `feature-auth` |
+| Branch | `{type}/{N}-{slug}` | `fix/1-login-bug`, `feat/13-dark-mode` |
 
 > Note: PRs and Issues share the same namespace in GitHub.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yeongjaeyou/claude-code-config",
-  "version": "0.19.0",
+  "version": "0.21.0",
   "description": "Claude Code CLI custom commands, agents, and skills",
   "bin": {
     "claude-code-config": "./bin/cli.js"