@yeongjaeyou/claude-code-config 0.20.0 → 0.21.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -6,6 +6,12 @@ description: Resolve GitHub Issue
|
|
|
6
6
|
|
|
7
7
|
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`.
|
|
8
8
|
|
|
9
|
+
## Prerequisites
|
|
10
|
+
|
|
11
|
+
Before starting the workflow:
|
|
12
|
+
- **Serena MCP**: If not already active, run `activate_project` to enable semantic code analysis tools
|
|
13
|
+
- **Clean state**: Ensure no uncommitted changes that could conflict with the new branch
|
|
14
|
+
|
|
9
15
|
## Workflow
|
|
10
16
|
|
|
11
17
|
1. **Analyze Issue**:
|
|
@@ -44,18 +50,30 @@ Act as an expert developer who systematically analyzes and resolves GitHub issue
|
|
|
44
50
|
```
|
|
45
51
|
- Skip if Status field does not exist
|
|
46
52
|
|
|
47
|
-
5. **Analyze Codebase (MANDATORY)**: Before writing any code,
|
|
53
|
+
5. **Analyze Codebase (MANDATORY)**: Before writing any code, understand the affected areas:
|
|
54
|
+
|
|
55
|
+
**Tool Selection by Scope:**
|
|
56
|
+
| Scope | Approach |
|
|
57
|
+
|-------|----------|
|
|
58
|
+
| **Narrow** (1-2 files, specific function) | Serena: `get_symbols_overview` → `find_symbol` → `find_referencing_symbols` |
|
|
59
|
+
| **Broad** (multiple modules, architecture) | Explorer agents in parallel (preserves main context) |
|
|
60
|
+
|
|
61
|
+
**For broad changes**, spawn 2-3 Explorer agents simultaneously:
|
|
48
62
|
- **Structure agent**: Overall architecture and file relationships
|
|
49
63
|
- **Pattern agent**: Similar implementations in codebase
|
|
50
64
|
- **Dependency agent**: Affected modules and consumers
|
|
51
65
|
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
66
|
+
**For narrow changes**, use Serena directly:
|
|
67
|
+
1. `get_symbols_overview` on target file(s)
|
|
68
|
+
2. `find_symbol` with `include_body=True` for specific functions
|
|
69
|
+
3. `find_referencing_symbols` for impact analysis
|
|
55
70
|
|
|
56
71
|
6. **Plan Resolution**: Based on analysis results, develop a concrete resolution plan and define work steps.
|
|
57
72
|
|
|
58
|
-
7. **Resolve Issue**:
|
|
73
|
+
7. **Resolve Issue**: Implement the solution using appropriate tools:
|
|
74
|
+
- **Symbolic edits** (Serena): `replace_symbol_body`, `insert_after_symbol` for precise modifications
|
|
75
|
+
- **File edits**: For non-code files or complex multi-line changes
|
|
76
|
+
- **Sub-agents**: For large-scale parallel modifications
|
|
59
77
|
- **If TDD enabled** (marker detected in Step 1):
|
|
60
78
|
- **Reference**: See `feature-planner` skill for detailed TDD methodology
|
|
61
79
|
1. 🔴 RED: Write failing tests first based on requirements
|