pulse-coder-cli 0.0.1-alpha.1
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.
- package/.pulse-coder/agents/code-reviewer.md +36 -0
- package/.pulse-coder/agents/doc-generator.md +37 -0
- package/.pulse-coder/agents/test-writer.md +38 -0
- package/.pulse-coder/mcp.json +8 -0
- package/.pulse-coder/skills/branch-naming/SKILL.md +427 -0
- package/.pulse-coder/skills/code-review/SKILL.md +56 -0
- package/.pulse-coder/skills/deep-research/SKILL.md +124 -0
- package/.pulse-coder/skills/git-workflow/SKILL.md +93 -0
- package/.pulse-coder/skills/mr-generator/README.md +96 -0
- package/.pulse-coder/skills/mr-generator/SKILL.md +113 -0
- package/.pulse-coder/skills/mr-generator/mr-generate.sh +342 -0
- package/.pulse-coder/skills/refactor/SKILL.md +63 -0
- package/README.md +155 -0
- package/dist/index.js +599 -0
- package/dist/index.js.map +1 -0
- package/package.json +25 -0
- package/src/index.ts +321 -0
- package/src/input-manager.ts +113 -0
- package/src/session-commands.ts +142 -0
- package/src/session.ts +171 -0
- package/tsconfig.json +9 -0
- package/tsup.config.ts +12 -0
|
@@ -0,0 +1,124 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: deep-research
|
|
3
|
+
description: Conduct comprehensive multi-round research using iterative web searches to gather, analyze, and synthesize information
|
|
4
|
+
version: 1.0.0
|
|
5
|
+
author: Pulse Coder Team
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Deep Research Skill
|
|
9
|
+
|
|
10
|
+
This skill enables comprehensive research through iterative web searches, allowing you to explore topics in depth by conducting 5-10 rounds of focused searches.
|
|
11
|
+
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
Use deep-research when you need to:
|
|
15
|
+
- Gather comprehensive information on complex topics
|
|
16
|
+
- Compare multiple approaches or solutions
|
|
17
|
+
- Understand emerging technologies or trends
|
|
18
|
+
- Research best practices across different sources
|
|
19
|
+
- Investigate technical problems with multiple facets
|
|
20
|
+
- Build a complete picture of a topic before making decisions
|
|
21
|
+
|
|
22
|
+
## Research Process
|
|
23
|
+
|
|
24
|
+
### 1. Initial Exploration (Rounds 1-2)
|
|
25
|
+
- Start with broad search queries to understand the topic landscape
|
|
26
|
+
- Identify key concepts, technologies, and terminology
|
|
27
|
+
- Note knowledge gaps and areas requiring deeper investigation
|
|
28
|
+
|
|
29
|
+
### 2. Focused Investigation (Rounds 3-6)
|
|
30
|
+
- Refine queries based on initial findings
|
|
31
|
+
- Dive deeper into specific subtopics
|
|
32
|
+
- Compare different approaches or solutions
|
|
33
|
+
- Gather technical details and implementation examples
|
|
34
|
+
- Look for authoritative sources and documentation
|
|
35
|
+
|
|
36
|
+
### 3. Synthesis & Validation (Rounds 7-10)
|
|
37
|
+
- Cross-reference information from multiple sources
|
|
38
|
+
- Validate findings with official documentation
|
|
39
|
+
- Look for recent updates or changes (2024-2026)
|
|
40
|
+
- Identify consensus vs. controversial aspects
|
|
41
|
+
- Fill remaining knowledge gaps
|
|
42
|
+
|
|
43
|
+
## Using the Tavily Tool
|
|
44
|
+
|
|
45
|
+
The `tavily` tool is available for web searches:
|
|
46
|
+
|
|
47
|
+
```typescript
|
|
48
|
+
// Example usage
|
|
49
|
+
await tavily.execute({
|
|
50
|
+
query: "your search query here",
|
|
51
|
+
maxResults: 5 // Optional, defaults to 5
|
|
52
|
+
});
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
## Search Strategy Tips
|
|
56
|
+
|
|
57
|
+
**Progressive Refinement**
|
|
58
|
+
- Round 1-2: Broad overview queries
|
|
59
|
+
- Round 3-5: Specific technical details
|
|
60
|
+
- Round 6-8: Edge cases and best practices
|
|
61
|
+
- Round 9-10: Recent updates and validation
|
|
62
|
+
|
|
63
|
+
**Query Formulation**
|
|
64
|
+
- Use specific technical terms when available
|
|
65
|
+
- Include year (2024-2026) for recent information
|
|
66
|
+
- Combine technology names with action words (e.g., "implement", "compare", "best practices")
|
|
67
|
+
- Ask about trade-offs and limitations
|
|
68
|
+
|
|
69
|
+
**Information Quality**
|
|
70
|
+
- Prioritize official documentation
|
|
71
|
+
- Look for recent blog posts from experts
|
|
72
|
+
- Check GitHub repositories for real examples
|
|
73
|
+
- Compare multiple sources for accuracy
|
|
74
|
+
|
|
75
|
+
## Output Structure
|
|
76
|
+
|
|
77
|
+
Present your research findings in this format:
|
|
78
|
+
|
|
79
|
+
**Overview**
|
|
80
|
+
- Brief summary of the topic
|
|
81
|
+
- Key findings and main takeaways
|
|
82
|
+
|
|
83
|
+
**Detailed Findings**
|
|
84
|
+
- Organized by subtopic or theme
|
|
85
|
+
- Include specific technical details
|
|
86
|
+
- Reference sources for important claims
|
|
87
|
+
|
|
88
|
+
**Comparison & Trade-offs** (if applicable)
|
|
89
|
+
- Different approaches or solutions
|
|
90
|
+
- Pros and cons of each
|
|
91
|
+
- Recommended scenarios for each option
|
|
92
|
+
|
|
93
|
+
**Implementation Guidance** (if applicable)
|
|
94
|
+
- Step-by-step approach
|
|
95
|
+
- Code examples or patterns
|
|
96
|
+
- Common pitfalls to avoid
|
|
97
|
+
|
|
98
|
+
**Sources**
|
|
99
|
+
- List all URLs consulted
|
|
100
|
+
- Group by relevance or topic
|
|
101
|
+
|
|
102
|
+
## Example Research Flow
|
|
103
|
+
|
|
104
|
+
**Topic: "Best practices for React Server Components in Next.js 14"**
|
|
105
|
+
|
|
106
|
+
Round 1: "React Server Components overview 2024"
|
|
107
|
+
Round 2: "Next.js 14 Server Components features"
|
|
108
|
+
Round 3: "Server Components vs Client Components when to use"
|
|
109
|
+
Round 4: "React Server Components data fetching patterns"
|
|
110
|
+
Round 5: "Next.js 14 Server Components performance"
|
|
111
|
+
Round 6: "Server Components best practices 2024"
|
|
112
|
+
Round 7: "Common mistakes React Server Components"
|
|
113
|
+
Round 8: "Server Components with Suspense and streaming"
|
|
114
|
+
Round 9: "Production experiences Server Components"
|
|
115
|
+
Round 10: "Server Components migration guide"
|
|
116
|
+
|
|
117
|
+
## Important Notes
|
|
118
|
+
|
|
119
|
+
- Each search builds on previous findings
|
|
120
|
+
- Adapt your strategy based on what you learn
|
|
121
|
+
- Don't repeat identical queries
|
|
122
|
+
- Balance breadth and depth appropriately
|
|
123
|
+
- Always cite sources in your final output
|
|
124
|
+
- Focus on actionable insights, not just information gathering
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: git-workflow
|
|
3
|
+
description: Standard git workflow for handling staged changes on existing branch - add, commit, and push
|
|
4
|
+
description_zh: 在现有分支上处理已暂存代码的标准 git 工作流程 - 添加、提交和推送
|
|
5
|
+
version: 1.2.0
|
|
6
|
+
author: Pulse Coder Team
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Git Workflow Skill
|
|
10
|
+
|
|
11
|
+
这个 skill 提供了一个简化的 git 工作流程,专注于在当前分支上处理更改,不创建新分支。
|
|
12
|
+
|
|
13
|
+
## 工作流程步骤
|
|
14
|
+
|
|
15
|
+
### 1. 检查当前状态
|
|
16
|
+
```bash
|
|
17
|
+
git status
|
|
18
|
+
```
|
|
19
|
+
检查当前分支状态,识别:
|
|
20
|
+
- 已修改的文件 (modified files)
|
|
21
|
+
- 未跟踪的文件 (untracked files)
|
|
22
|
+
- 已暂存的文件 (staged files)
|
|
23
|
+
|
|
24
|
+
### 2. 添加更改到暂存区
|
|
25
|
+
```bash
|
|
26
|
+
git add <files...>
|
|
27
|
+
```
|
|
28
|
+
根据情况选择:
|
|
29
|
+
- `git add .` - 添加所有更改
|
|
30
|
+
- `git add -A` - 添加所有文件(包括删除的)
|
|
31
|
+
- `git add <specific-files>` - 只添加特定文件
|
|
32
|
+
|
|
33
|
+
### 3. 提交更改
|
|
34
|
+
```bash
|
|
35
|
+
git commit -m "<type>: <short description>"
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
提交消息格式:
|
|
39
|
+
```
|
|
40
|
+
<type>: <short description>
|
|
41
|
+
|
|
42
|
+
- <详细描述点1>
|
|
43
|
+
- <详细描述点2>
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
类型包括:
|
|
47
|
+
- `feat` - 新功能
|
|
48
|
+
- `fix` - 修复
|
|
49
|
+
- `refactor` - 重构
|
|
50
|
+
- `docs` - 文档
|
|
51
|
+
- `style` - 格式调整
|
|
52
|
+
- `test` - 测试
|
|
53
|
+
- `chore` - 构建/工具
|
|
54
|
+
|
|
55
|
+
### 4. 推送到远程仓库
|
|
56
|
+
```bash
|
|
57
|
+
git push
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
## 快速工作流程
|
|
61
|
+
|
|
62
|
+
```bash
|
|
63
|
+
# 一键完成
|
|
64
|
+
git status
|
|
65
|
+
git add .
|
|
66
|
+
git commit -m "描述更改内容"
|
|
67
|
+
git push
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
## 选择性工作流程
|
|
71
|
+
|
|
72
|
+
### 只添加特定文件
|
|
73
|
+
```bash
|
|
74
|
+
git add src/ docs/
|
|
75
|
+
git commit -m "feat: 更新核心功能和文档"
|
|
76
|
+
git push
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
### 分批次提交
|
|
80
|
+
```bash
|
|
81
|
+
git add src/app.ts
|
|
82
|
+
git commit -m "feat: 添加新功能"
|
|
83
|
+
git add tests/
|
|
84
|
+
git commit -m "test: 添加对应测试"
|
|
85
|
+
git push
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
## 验证步骤
|
|
89
|
+
|
|
90
|
+
完成每个步骤后验证:
|
|
91
|
+
1. `git status` - 确认工作目录干净
|
|
92
|
+
2. `git log --oneline -3` - 查看最新提交
|
|
93
|
+
3. `git branch` - 确认当前分支
|
|
@@ -0,0 +1,96 @@
|
|
|
1
|
+
# MR Generator Skill
|
|
2
|
+
|
|
3
|
+
Automatically generate concise English MR titles and descriptions based on diff between current branch and remote master.
|
|
4
|
+
|
|
5
|
+
## Quick Start
|
|
6
|
+
|
|
7
|
+
```bash
|
|
8
|
+
# Make it globally available
|
|
9
|
+
ln -sf "$(pwd)/.coder/skills/mr-generator/mr-generate.sh" /usr/local/bin/mr-generate
|
|
10
|
+
|
|
11
|
+
# Basic usage
|
|
12
|
+
mr-generate
|
|
13
|
+
|
|
14
|
+
# With options
|
|
15
|
+
mr-generate --target origin/develop
|
|
16
|
+
mr-generate --preview
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
## Integration Examples
|
|
20
|
+
|
|
21
|
+
### GitHub CLI
|
|
22
|
+
```bash
|
|
23
|
+
# Create MR with auto-generated title/description
|
|
24
|
+
git push origin HEAD
|
|
25
|
+
mr-generate | gh pr create --title "$(head -1)" --body "$(tail -n +3)"
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
### GitLab CLI
|
|
29
|
+
```bash
|
|
30
|
+
# GitLab MR creation
|
|
31
|
+
git push origin HEAD
|
|
32
|
+
mr-generate | glab mr create --title "$(head -1)" --description "$(tail -n +3)"
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
### Manual Copy
|
|
36
|
+
```bash
|
|
37
|
+
# Preview before creating MR
|
|
38
|
+
mr-generate --preview
|
|
39
|
+
# Then copy title/description manually
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
## How It Works
|
|
43
|
+
|
|
44
|
+
1. **Diff Analysis**: Compares current branch with target (default: origin/master)
|
|
45
|
+
2. **Change Classification**: Analyzes file types and patterns
|
|
46
|
+
3. **Module Detection**: Identifies main functional areas
|
|
47
|
+
4. **Smart Generation**: Creates context-appropriate titles and descriptions
|
|
48
|
+
|
|
49
|
+
## Output Examples
|
|
50
|
+
|
|
51
|
+
### Feature Development
|
|
52
|
+
```
|
|
53
|
+
Add user authentication with JWT
|
|
54
|
+
|
|
55
|
+
Implement secure user authentication using JWT tokens
|
|
56
|
+
|
|
57
|
+
- Add login/logout endpoints
|
|
58
|
+
- Implement token validation middleware
|
|
59
|
+
- Add user registration flow
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
### Bug Fix
|
|
63
|
+
```
|
|
64
|
+
Fix email validation in login form
|
|
65
|
+
|
|
66
|
+
Resolve email format validation issue causing login failures
|
|
67
|
+
|
|
68
|
+
- Update email regex pattern
|
|
69
|
+
- Add proper error handling
|
|
70
|
+
- Add validation tests
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
### Refactoring
|
|
74
|
+
```
|
|
75
|
+
Refactor API response handling
|
|
76
|
+
|
|
77
|
+
Improve API response consistency and error handling
|
|
78
|
+
|
|
79
|
+
- Standardize response format
|
|
80
|
+
- Add centralized error handling
|
|
81
|
+
- Reduce code duplication
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
## Configuration
|
|
85
|
+
|
|
86
|
+
### Environment Variables
|
|
87
|
+
```bash
|
|
88
|
+
export MR_TARGET_BRANCH=origin/main # Default target branch
|
|
89
|
+
export MR_MAX_TITLE_LENGTH=50 # Title length limit
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
### Git Aliases
|
|
93
|
+
```bash
|
|
94
|
+
git config alias.mr-title "!.coder/skills/mr-generator/mr-generate.sh"
|
|
95
|
+
git config alias.mr-preview "!.coder/skills/mr-generator/mr-generate.sh --preview"
|
|
96
|
+
```
|
|
@@ -0,0 +1,113 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: mr-generator
|
|
3
|
+
description: Automatically generate concise MR titles and descriptions based on current branch diff
|
|
4
|
+
description_zh: 基于当前分支与远程 master 的 diff 自动生成简洁英文 MR 标题和描述的 skill。
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
author: Pulse Coder Team
|
|
7
|
+
---
|
|
8
|
+
# MR Generator Skill
|
|
9
|
+
|
|
10
|
+
基于当前分支与远程 master 的 diff 自动生成简洁英文 MR 标题和描述的 skill。
|
|
11
|
+
|
|
12
|
+
## 核心功能
|
|
13
|
+
|
|
14
|
+
### 1. 智能 diff 分析
|
|
15
|
+
- 分析文件变更类型和范围
|
|
16
|
+
- 识别主要功能模块
|
|
17
|
+
- 提取关键变更点
|
|
18
|
+
|
|
19
|
+
### 2. 自动标题生成
|
|
20
|
+
- 基于变更类型选择合适的动词
|
|
21
|
+
- 包含主要功能模块
|
|
22
|
+
- 保持在 50 字符以内
|
|
23
|
+
|
|
24
|
+
### 3. 简洁描述生成
|
|
25
|
+
- 列出核心变更点
|
|
26
|
+
- 使用项目符号格式
|
|
27
|
+
- 英文简洁表达
|
|
28
|
+
|
|
29
|
+
## 使用方式
|
|
30
|
+
|
|
31
|
+
### 基本使用
|
|
32
|
+
```bash
|
|
33
|
+
# 生成 MR 标题和描述
|
|
34
|
+
./mr-generate.sh
|
|
35
|
+
|
|
36
|
+
# 指定目标分支(默认 origin/master)
|
|
37
|
+
./mr-generate.sh --target origin/develop
|
|
38
|
+
|
|
39
|
+
# 预览模式
|
|
40
|
+
./mr-generate.sh --preview
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
### 集成到工作流
|
|
44
|
+
```bash
|
|
45
|
+
# 在创建 MR 前运行
|
|
46
|
+
git push origin HEAD
|
|
47
|
+
./mr-generate.sh | gh pr create --title "$(head -1)" --body "$(tail -n +3)"
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
## 标题生成规则
|
|
51
|
+
|
|
52
|
+
### 变更类型映射
|
|
53
|
+
- **新功能**: Add / Implement / Introduce
|
|
54
|
+
- **修复**: Fix / Resolve / Correct
|
|
55
|
+
- **重构**: Refactor / Improve / Optimize
|
|
56
|
+
- **文档**: Update / Add docs
|
|
57
|
+
- **测试**: Add tests / Improve coverage
|
|
58
|
+
- **配置**: Update config / Setup
|
|
59
|
+
|
|
60
|
+
### 模块提取
|
|
61
|
+
- 基于文件路径识别主要模块
|
|
62
|
+
- 优先使用业务功能名称
|
|
63
|
+
- 简洁技术术语
|
|
64
|
+
|
|
65
|
+
## 描述格式
|
|
66
|
+
|
|
67
|
+
```
|
|
68
|
+
Brief description of changes
|
|
69
|
+
|
|
70
|
+
- Key change 1
|
|
71
|
+
- Key change 2
|
|
72
|
+
- Impact or improvement
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
## 示例输出
|
|
76
|
+
|
|
77
|
+
### 功能开发
|
|
78
|
+
**标题**: `Add user authentication with JWT`
|
|
79
|
+
|
|
80
|
+
**描述**:
|
|
81
|
+
```
|
|
82
|
+
Implement secure user authentication using JWT tokens
|
|
83
|
+
|
|
84
|
+
- Add login/logout endpoints
|
|
85
|
+
- Implement token validation middleware
|
|
86
|
+
- Add user registration flow
|
|
87
|
+
- Update API documentation
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
### Bug 修复
|
|
91
|
+
**标题**: `Fix login validation error`
|
|
92
|
+
|
|
93
|
+
**描述**:
|
|
94
|
+
```
|
|
95
|
+
Resolve email validation issue in user login
|
|
96
|
+
|
|
97
|
+
- Fix regex pattern for email validation
|
|
98
|
+
- Add proper error handling for invalid formats
|
|
99
|
+
- Update unit tests for edge cases
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
### 重构
|
|
103
|
+
**标题**: `Refactor API response handling`
|
|
104
|
+
|
|
105
|
+
**描述**:
|
|
106
|
+
```
|
|
107
|
+
Improve API response consistency and error handling
|
|
108
|
+
|
|
109
|
+
- Standardize response format across endpoints
|
|
110
|
+
- Add centralized error handling middleware
|
|
111
|
+
- Reduce code duplication in controllers
|
|
112
|
+
- Update test assertions
|
|
113
|
+
```
|