monoco-toolkit 0.3.9__py3-none-any.whl → 0.3.11__py3-none-any.whl
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.
- monoco/__main__.py +8 -0
- monoco/core/artifacts/__init__.py +16 -0
- monoco/core/artifacts/manager.py +575 -0
- monoco/core/artifacts/models.py +161 -0
- monoco/core/config.py +38 -4
- monoco/core/git.py +23 -0
- monoco/core/hooks/builtin/git_cleanup.py +1 -1
- monoco/core/ingestion/__init__.py +20 -0
- monoco/core/ingestion/discovery.py +248 -0
- monoco/core/ingestion/watcher.py +343 -0
- monoco/core/ingestion/worker.py +436 -0
- monoco/core/injection.py +63 -29
- monoco/core/integrations.py +2 -2
- monoco/core/loader.py +633 -0
- monoco/core/output.py +5 -5
- monoco/core/registry.py +34 -19
- monoco/core/resource/__init__.py +5 -0
- monoco/core/resource/finder.py +98 -0
- monoco/core/resource/manager.py +91 -0
- monoco/core/resource/models.py +35 -0
- monoco/core/skill_framework.py +292 -0
- monoco/core/skills.py +524 -385
- monoco/core/sync.py +73 -1
- monoco/core/workflow_converter.py +420 -0
- monoco/daemon/app.py +77 -1
- monoco/daemon/commands.py +10 -0
- monoco/daemon/mailroom_service.py +196 -0
- monoco/daemon/models.py +1 -0
- monoco/daemon/scheduler.py +236 -0
- monoco/daemon/services.py +185 -0
- monoco/daemon/triggers.py +55 -0
- monoco/features/agent/__init__.py +2 -2
- monoco/features/agent/adapter.py +41 -0
- monoco/features/agent/apoptosis.py +44 -0
- monoco/features/agent/cli.py +101 -144
- monoco/features/agent/config.py +35 -21
- monoco/features/agent/defaults.py +6 -49
- monoco/features/agent/engines.py +32 -6
- monoco/features/agent/manager.py +47 -6
- monoco/features/agent/models.py +2 -2
- monoco/features/agent/resources/atoms/atom-code-dev.yaml +61 -0
- monoco/features/agent/resources/atoms/atom-issue-lifecycle.yaml +73 -0
- monoco/features/agent/resources/atoms/atom-knowledge.yaml +55 -0
- monoco/features/agent/resources/atoms/atom-review.yaml +60 -0
- monoco/{core/resources/en → features/agent/resources/en/skills/monoco_atom_core}/SKILL.md +3 -1
- monoco/features/agent/resources/en/skills/monoco_workflow_agent_engineer/SKILL.md +94 -0
- monoco/features/agent/resources/en/skills/monoco_workflow_agent_manager/SKILL.md +93 -0
- monoco/features/agent/resources/en/skills/monoco_workflow_agent_planner/SKILL.md +85 -0
- monoco/features/agent/resources/en/skills/monoco_workflow_agent_reviewer/SKILL.md +114 -0
- monoco/features/agent/resources/workflows/workflow-dev.yaml +83 -0
- monoco/features/agent/resources/workflows/workflow-issue-create.yaml +72 -0
- monoco/features/agent/resources/workflows/workflow-review.yaml +94 -0
- monoco/features/agent/resources/zh/roles/monoco_role_engineer.yaml +49 -0
- monoco/features/agent/resources/zh/roles/monoco_role_manager.yaml +46 -0
- monoco/features/agent/resources/zh/roles/monoco_role_planner.yaml +46 -0
- monoco/features/agent/resources/zh/roles/monoco_role_reviewer.yaml +47 -0
- monoco/{core/resources/zh → features/agent/resources/zh/skills/monoco_atom_core}/SKILL.md +3 -1
- monoco/features/agent/resources/{skills/flow_engineer → zh/skills/monoco_workflow_agent_engineer}/SKILL.md +2 -2
- monoco/features/agent/resources/{skills/flow_manager → zh/skills/monoco_workflow_agent_manager}/SKILL.md +2 -2
- monoco/features/agent/resources/zh/skills/monoco_workflow_agent_planner/SKILL.md +259 -0
- monoco/features/agent/resources/zh/skills/monoco_workflow_agent_reviewer/SKILL.md +137 -0
- monoco/features/agent/session.py +59 -11
- monoco/features/agent/worker.py +38 -2
- monoco/features/artifact/__init__.py +0 -0
- monoco/features/artifact/adapter.py +33 -0
- monoco/features/artifact/resources/zh/AGENTS.md +14 -0
- monoco/features/artifact/resources/zh/skills/monoco_atom_artifact/SKILL.md +278 -0
- monoco/features/glossary/__init__.py +0 -0
- monoco/features/glossary/adapter.py +42 -0
- monoco/features/glossary/config.py +5 -0
- monoco/features/glossary/resources/en/AGENTS.md +29 -0
- monoco/features/glossary/resources/en/skills/monoco_atom_glossary/SKILL.md +35 -0
- monoco/features/glossary/resources/zh/AGENTS.md +29 -0
- monoco/features/glossary/resources/zh/skills/monoco_atom_glossary/SKILL.md +35 -0
- monoco/features/hooks/__init__.py +11 -0
- monoco/features/hooks/adapter.py +67 -0
- monoco/features/hooks/commands.py +309 -0
- monoco/features/hooks/core.py +441 -0
- monoco/features/hooks/resources/ADDING_HOOKS.md +234 -0
- monoco/features/i18n/adapter.py +18 -5
- monoco/features/i18n/core.py +482 -17
- monoco/features/i18n/resources/en/{SKILL.md → skills/monoco_atom_i18n/SKILL.md} +3 -1
- monoco/features/i18n/resources/en/skills/monoco_workflow_i18n_scan/SKILL.md +105 -0
- monoco/features/i18n/resources/zh/{SKILL.md → skills/monoco_atom_i18n/SKILL.md} +3 -1
- monoco/features/i18n/resources/{skills/i18n_scan_workflow → zh/skills/monoco_workflow_i18n_scan}/SKILL.md +2 -2
- monoco/features/issue/adapter.py +19 -6
- monoco/features/issue/commands.py +281 -7
- monoco/features/issue/core.py +272 -19
- monoco/features/issue/engine/machine.py +118 -5
- monoco/features/issue/linter.py +60 -5
- monoco/features/issue/models.py +3 -2
- monoco/features/issue/resources/en/AGENTS.md +109 -0
- monoco/features/issue/resources/en/{SKILL.md → skills/monoco_atom_issue/SKILL.md} +3 -1
- monoco/features/issue/resources/en/skills/monoco_workflow_issue_creation/SKILL.md +167 -0
- monoco/features/issue/resources/en/skills/monoco_workflow_issue_development/SKILL.md +224 -0
- monoco/features/issue/resources/en/skills/monoco_workflow_issue_management/SKILL.md +159 -0
- monoco/features/issue/resources/en/skills/monoco_workflow_issue_refinement/SKILL.md +203 -0
- monoco/features/issue/resources/hooks/post-checkout.sh +39 -0
- monoco/features/issue/resources/hooks/pre-commit.sh +41 -0
- monoco/features/issue/resources/hooks/pre-push.sh +35 -0
- monoco/features/issue/resources/zh/AGENTS.md +109 -0
- monoco/features/issue/resources/zh/{SKILL.md → skills/monoco_atom_issue_lifecycle/SKILL.md} +3 -1
- monoco/features/issue/resources/zh/skills/monoco_workflow_issue_creation/SKILL.md +167 -0
- monoco/features/issue/resources/zh/skills/monoco_workflow_issue_development/SKILL.md +224 -0
- monoco/features/issue/resources/{skills/issue_lifecycle_workflow → zh/skills/monoco_workflow_issue_management}/SKILL.md +2 -2
- monoco/features/issue/resources/zh/skills/monoco_workflow_issue_refinement/SKILL.md +203 -0
- monoco/features/issue/validator.py +101 -1
- monoco/features/memo/adapter.py +21 -8
- monoco/features/memo/cli.py +103 -10
- monoco/features/memo/core.py +178 -92
- monoco/features/memo/models.py +53 -0
- monoco/features/memo/resources/en/skills/monoco_atom_memo/SKILL.md +77 -0
- monoco/features/memo/resources/en/skills/monoco_workflow_note_processing/SKILL.md +140 -0
- monoco/features/memo/resources/zh/{SKILL.md → skills/monoco_atom_memo/SKILL.md} +3 -1
- monoco/features/memo/resources/{skills/note_processing_workflow → zh/skills/monoco_workflow_note_processing}/SKILL.md +2 -2
- monoco/features/spike/adapter.py +18 -5
- monoco/features/spike/resources/en/{SKILL.md → skills/monoco_atom_spike/SKILL.md} +3 -1
- monoco/features/spike/resources/en/skills/monoco_workflow_research/SKILL.md +121 -0
- monoco/features/spike/resources/zh/{SKILL.md → skills/monoco_atom_spike/SKILL.md} +3 -1
- monoco/features/spike/resources/{skills/research_workflow → zh/skills/monoco_workflow_research}/SKILL.md +2 -2
- monoco/main.py +38 -1
- monoco_toolkit-0.3.11.dist-info/METADATA +130 -0
- monoco_toolkit-0.3.11.dist-info/RECORD +181 -0
- monoco/features/agent/reliability.py +0 -106
- monoco/features/agent/resources/skills/flow_reviewer/SKILL.md +0 -114
- monoco_toolkit-0.3.9.dist-info/METADATA +0 -127
- monoco_toolkit-0.3.9.dist-info/RECORD +0 -115
- /monoco/{core → features/agent}/resources/en/AGENTS.md +0 -0
- /monoco/{core → features/agent}/resources/zh/AGENTS.md +0 -0
- {monoco_toolkit-0.3.9.dist-info → monoco_toolkit-0.3.11.dist-info}/WHEEL +0 -0
- {monoco_toolkit-0.3.9.dist-info → monoco_toolkit-0.3.11.dist-info}/entry_points.txt +0 -0
- {monoco_toolkit-0.3.9.dist-info → monoco_toolkit-0.3.11.dist-info}/licenses/LICENSE +0 -0
|
@@ -0,0 +1,114 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: monoco_workflow_agent_reviewer
|
|
3
|
+
description: Standardized workflow for the Reviewer role (Flow Skill). Defines the standard operating procedure from code checkout to adversarial testing to review completion, ensuring code quality and process compliance.
|
|
4
|
+
type: workflow
|
|
5
|
+
role: reviewer
|
|
6
|
+
version: 1.0.0
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Reviewer Flow
|
|
10
|
+
|
|
11
|
+
Standardized workflow for the Reviewer role, ensuring thorough code review and quality assurance.
|
|
12
|
+
|
|
13
|
+
## Workflow State Machine
|
|
14
|
+
|
|
15
|
+
```mermaid
|
|
16
|
+
stateDiagram-v2
|
|
17
|
+
[*] --> Checkout: Start Review
|
|
18
|
+
|
|
19
|
+
Checkout --> Review: Code Ready
|
|
20
|
+
|
|
21
|
+
Review --> Test: Code Review Passed
|
|
22
|
+
Review --> Review: Issues Found<br/>(Request Changes)
|
|
23
|
+
|
|
24
|
+
Test --> Approve: Tests Pass
|
|
25
|
+
Test --> Test: Issues Found<br/>(Report Bugs)
|
|
26
|
+
|
|
27
|
+
Approve --> [*]: Review Complete
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
## Execution Steps
|
|
31
|
+
|
|
32
|
+
### 1. Checkout (检出)
|
|
33
|
+
|
|
34
|
+
- **Goal**: Set up review environment
|
|
35
|
+
- **Checkpoints**:
|
|
36
|
+
- [ ] Checkout the PR branch
|
|
37
|
+
- [ ] Review Issue description and acceptance criteria
|
|
38
|
+
- [ ] Check related files and context
|
|
39
|
+
- [ ] Run `monoco issue lint` to verify compliance
|
|
40
|
+
|
|
41
|
+
### 2. Review (审查)
|
|
42
|
+
|
|
43
|
+
- **Goal**: Thorough code review
|
|
44
|
+
- **Checkpoints**:
|
|
45
|
+
- [ ] Review code against acceptance criteria
|
|
46
|
+
- [ ] Check code style and conventions
|
|
47
|
+
- [ ] Verify error handling and edge cases
|
|
48
|
+
- [ ] Review test coverage and quality
|
|
49
|
+
- [ ] Check documentation updates
|
|
50
|
+
|
|
51
|
+
### 3. Test (测试)
|
|
52
|
+
|
|
53
|
+
- **Goal**: Adversarial testing and verification
|
|
54
|
+
- **Checkpoints**:
|
|
55
|
+
- [ ] Run full test suite
|
|
56
|
+
- [ ] Perform manual testing if needed
|
|
57
|
+
- [ ] Test edge cases and error scenarios
|
|
58
|
+
- [ ] Verify integration points
|
|
59
|
+
|
|
60
|
+
### 4. Approve (批准)
|
|
61
|
+
|
|
62
|
+
- **Goal**: Complete review with decision
|
|
63
|
+
- **Checkpoints**:
|
|
64
|
+
- [ ] Summarize review findings
|
|
65
|
+
- [ ] Provide constructive feedback
|
|
66
|
+
- [ ] Update Issue status if needed
|
|
67
|
+
- [ ] Record review comments in Issue
|
|
68
|
+
|
|
69
|
+
## Review Checklist
|
|
70
|
+
|
|
71
|
+
### Code Quality
|
|
72
|
+
- [ ] Code follows project conventions
|
|
73
|
+
- [ ] No obvious bugs or logic errors
|
|
74
|
+
- [ ] Proper error handling
|
|
75
|
+
- [ ] Adequate logging (where appropriate)
|
|
76
|
+
|
|
77
|
+
### Testing
|
|
78
|
+
- [ ] Unit tests cover new code
|
|
79
|
+
- [ ] Integration tests pass
|
|
80
|
+
- [ ] Edge cases are tested
|
|
81
|
+
- [ ] No flaky tests introduced
|
|
82
|
+
|
|
83
|
+
### Documentation
|
|
84
|
+
- [ ] Code comments are clear and helpful
|
|
85
|
+
- [ ] Public APIs are documented
|
|
86
|
+
- [ ] README/docs updated if needed
|
|
87
|
+
|
|
88
|
+
### Security
|
|
89
|
+
- [ ] No hardcoded secrets
|
|
90
|
+
- [ ] Input validation in place
|
|
91
|
+
- [ ] No SQL injection or XSS vulnerabilities
|
|
92
|
+
|
|
93
|
+
## Review Comments Format
|
|
94
|
+
|
|
95
|
+
```markdown
|
|
96
|
+
## Review Comments
|
|
97
|
+
|
|
98
|
+
### [File:Line] Issue Type: Brief Description
|
|
99
|
+
|
|
100
|
+
**Severity**: [blocking|major|minor|nit]
|
|
101
|
+
|
|
102
|
+
**Details**: Detailed explanation of the issue
|
|
103
|
+
|
|
104
|
+
**Suggestion**: How to fix or improve
|
|
105
|
+
|
|
106
|
+
---
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
## Best Practices
|
|
110
|
+
|
|
111
|
+
1. **Be Constructive**: Focus on the code, not the person
|
|
112
|
+
2. **Explain Why**: Always explain the reasoning behind suggestions
|
|
113
|
+
3. **Prioritize**: Distinguish between blocking issues and nits
|
|
114
|
+
4. **Respond Promptly**: Don't let reviews sit for too long
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: workflow-dev
|
|
3
|
+
type: workflow
|
|
4
|
+
description: 开发工作流编排 - 从准备环境到提交评审的完整流程
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
author: Monoco Toolkit
|
|
7
|
+
|
|
8
|
+
# 依赖的原子技能
|
|
9
|
+
dependencies:
|
|
10
|
+
- atom-issue-lifecycle
|
|
11
|
+
- atom-code-dev
|
|
12
|
+
|
|
13
|
+
# 工作流阶段定义
|
|
14
|
+
stages:
|
|
15
|
+
- name: setup
|
|
16
|
+
atom_skill: atom-issue-lifecycle
|
|
17
|
+
operation: start
|
|
18
|
+
description: 准备开发环境,创建功能分支
|
|
19
|
+
reminder: "确保使用 --branch 创建功能分支,禁止在 main/master 上开发"
|
|
20
|
+
next_stages:
|
|
21
|
+
success: investigate
|
|
22
|
+
branch_conflict: setup
|
|
23
|
+
|
|
24
|
+
- name: investigate
|
|
25
|
+
atom_skill: atom-code-dev
|
|
26
|
+
operation: investigate
|
|
27
|
+
description: 理解需求与上下文
|
|
28
|
+
reminder: "深入理解 Issue 需求,识别相关代码和依赖"
|
|
29
|
+
next_stages:
|
|
30
|
+
requirements_clear: implement
|
|
31
|
+
requirements_fuzzy: investigate
|
|
32
|
+
|
|
33
|
+
- name: implement
|
|
34
|
+
atom_skill: atom-code-dev
|
|
35
|
+
operation: implement
|
|
36
|
+
description: 实现代码变更
|
|
37
|
+
reminder: "遵循项目代码规范,小步提交,处理边界情况"
|
|
38
|
+
next_stages:
|
|
39
|
+
coding_complete: test
|
|
40
|
+
|
|
41
|
+
- name: test
|
|
42
|
+
atom_skill: atom-code-dev
|
|
43
|
+
operation: test
|
|
44
|
+
description: 运行测试确保代码质量
|
|
45
|
+
reminder: "所有测试必须通过,检查测试覆盖率"
|
|
46
|
+
next_stages:
|
|
47
|
+
test_passed: report
|
|
48
|
+
test_failed: implement
|
|
49
|
+
|
|
50
|
+
- name: report
|
|
51
|
+
atom_skill: atom-issue-lifecycle
|
|
52
|
+
operation: sync
|
|
53
|
+
description: 记录变更,更新文件追踪
|
|
54
|
+
reminder: "同步文件追踪,编写变更摘要"
|
|
55
|
+
next_stages:
|
|
56
|
+
report_complete: submit
|
|
57
|
+
|
|
58
|
+
- name: submit
|
|
59
|
+
atom_skill: atom-issue-lifecycle
|
|
60
|
+
operation: submit
|
|
61
|
+
description: 提交代码进行评审
|
|
62
|
+
reminder: "确保所有测试通过,lint 无错误后再提交"
|
|
63
|
+
next_stages:
|
|
64
|
+
submit_success: "[END]"
|
|
65
|
+
lint_failed: submit
|
|
66
|
+
|
|
67
|
+
# 执行模式配置
|
|
68
|
+
mode_config:
|
|
69
|
+
copilot:
|
|
70
|
+
behavior: "人类主导,AI 协助。每个 stage 前询问确认,在关键检查点暂停等待人类输入"
|
|
71
|
+
pause_on:
|
|
72
|
+
- setup
|
|
73
|
+
- implement
|
|
74
|
+
- submit
|
|
75
|
+
auto_execute: false
|
|
76
|
+
|
|
77
|
+
autopilot:
|
|
78
|
+
behavior: "AI 自动执行,按状态机流转,失败时暂停等待人类决策"
|
|
79
|
+
pause_on:
|
|
80
|
+
- test_failed
|
|
81
|
+
- lint_failed
|
|
82
|
+
- requirements_fuzzy
|
|
83
|
+
auto_execute: true
|
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: workflow-issue-create
|
|
3
|
+
type: workflow
|
|
4
|
+
description: Issue 创建工作流编排 - 从 Memo 提取到 Issue 创建
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
author: Monoco Toolkit
|
|
7
|
+
|
|
8
|
+
# 依赖的原子技能
|
|
9
|
+
dependencies:
|
|
10
|
+
- atom-knowledge
|
|
11
|
+
- atom-issue-lifecycle
|
|
12
|
+
|
|
13
|
+
# 工作流阶段定义
|
|
14
|
+
stages:
|
|
15
|
+
- name: extract
|
|
16
|
+
atom_skill: atom-knowledge
|
|
17
|
+
operation: process
|
|
18
|
+
description: 从 Memo 中提取改进线索
|
|
19
|
+
reminder: "运行 monoco memo list,分析每个 Memo 的改进类型和影响范围"
|
|
20
|
+
next_stages:
|
|
21
|
+
has_value: classify
|
|
22
|
+
no_value: archive
|
|
23
|
+
|
|
24
|
+
- name: classify
|
|
25
|
+
atom_skill: atom-issue-lifecycle
|
|
26
|
+
operation: create
|
|
27
|
+
description: 确定 Issue 类型和优先级
|
|
28
|
+
reminder: "判断类型 (Epic/Feature/Chore/Fix),评估是否需要前置架构设计"
|
|
29
|
+
next_stages:
|
|
30
|
+
needs_design: design
|
|
31
|
+
direct_create: create
|
|
32
|
+
|
|
33
|
+
- name: design
|
|
34
|
+
atom_skill: atom-code-dev
|
|
35
|
+
operation: investigate
|
|
36
|
+
description: 对复杂改进进行初步架构设计
|
|
37
|
+
reminder: "分析现有架构继承性,确定技术方案方向"
|
|
38
|
+
next_stages:
|
|
39
|
+
design_complete: create
|
|
40
|
+
|
|
41
|
+
- name: create
|
|
42
|
+
atom_skill: atom-issue-lifecycle
|
|
43
|
+
operation: create
|
|
44
|
+
description: 创建符合规范的 Issue
|
|
45
|
+
reminder: "编写清晰的描述和验收标准,确保至少 2 个 Checkbox"
|
|
46
|
+
next_stages:
|
|
47
|
+
create_success: "[END]"
|
|
48
|
+
|
|
49
|
+
- name: archive
|
|
50
|
+
atom_skill: atom-knowledge
|
|
51
|
+
operation: archive
|
|
52
|
+
description: 归档无直接改进价值的 Memo
|
|
53
|
+
reminder: "确认 Memo 内容为纯参考资料,记录归档原因"
|
|
54
|
+
next_stages:
|
|
55
|
+
archive_complete: "[END]"
|
|
56
|
+
|
|
57
|
+
# 执行模式配置
|
|
58
|
+
mode_config:
|
|
59
|
+
copilot:
|
|
60
|
+
behavior: "人类主导,AI 协助。主动提问、提供选项、协助起草、提醒合规"
|
|
61
|
+
pause_on:
|
|
62
|
+
- extract
|
|
63
|
+
- classify
|
|
64
|
+
- create
|
|
65
|
+
auto_execute: false
|
|
66
|
+
|
|
67
|
+
autopilot:
|
|
68
|
+
behavior: "AI 根据规则自动分类和创建,异常情况暂停"
|
|
69
|
+
pause_on:
|
|
70
|
+
- classification_unclear
|
|
71
|
+
- needs_human_decision
|
|
72
|
+
auto_execute: true
|
|
@@ -0,0 +1,94 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: workflow-review
|
|
3
|
+
type: workflow
|
|
4
|
+
description: 代码评审工作流编排 - 双层防御体系 (Verify + Challenge)
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
author: Monoco Toolkit
|
|
7
|
+
|
|
8
|
+
# 依赖的原子技能
|
|
9
|
+
dependencies:
|
|
10
|
+
- atom-review
|
|
11
|
+
|
|
12
|
+
# 工作流阶段定义
|
|
13
|
+
stages:
|
|
14
|
+
- name: checkout
|
|
15
|
+
atom_skill: atom-review
|
|
16
|
+
operation: checkout
|
|
17
|
+
description: 获取待评审的代码
|
|
18
|
+
reminder: "检出 PR/Branch,确认与 Base 分支的差异"
|
|
19
|
+
next_stages:
|
|
20
|
+
success: verify
|
|
21
|
+
|
|
22
|
+
- name: verify
|
|
23
|
+
atom_skill: atom-review
|
|
24
|
+
operation: verify
|
|
25
|
+
description: 验证 Engineer 提交的测试 (White-box)
|
|
26
|
+
reminder: "先运行 Engineer 编写的测试,验证功能正确性"
|
|
27
|
+
next_stages:
|
|
28
|
+
tests_passed: challenge
|
|
29
|
+
tests_failed: reject
|
|
30
|
+
|
|
31
|
+
- name: challenge
|
|
32
|
+
atom_skill: atom-review
|
|
33
|
+
operation: challenge
|
|
34
|
+
description: 对抗测试,尝试破坏代码 (Black-box)
|
|
35
|
+
reminder: "Try to break it - 寻找边界情况和安全漏洞"
|
|
36
|
+
next_stages:
|
|
37
|
+
challenge_passed: review
|
|
38
|
+
vulnerability_found: reject
|
|
39
|
+
|
|
40
|
+
- name: review
|
|
41
|
+
atom_skill: atom-review
|
|
42
|
+
operation: feedback
|
|
43
|
+
description: 代码审查,检查质量和可维护性
|
|
44
|
+
reminder: "检查功能、设计、可读性、文档、合规"
|
|
45
|
+
next_stages:
|
|
46
|
+
code_ok: approve
|
|
47
|
+
quality_issues: reject
|
|
48
|
+
minor_issues: request_changes
|
|
49
|
+
|
|
50
|
+
- name: approve
|
|
51
|
+
atom_skill: atom-review
|
|
52
|
+
operation: feedback
|
|
53
|
+
description: 批准代码合并
|
|
54
|
+
reminder: "代码健壮且符合规范,包含所有通过的 Challenge Tests"
|
|
55
|
+
next_stages:
|
|
56
|
+
success: cleanup
|
|
57
|
+
|
|
58
|
+
- name: reject
|
|
59
|
+
description: 拒绝,需要修改
|
|
60
|
+
reminder: "提供具体反馈,附带失败的 Test Case 或 Log"
|
|
61
|
+
next_stages:
|
|
62
|
+
success: "[END]"
|
|
63
|
+
|
|
64
|
+
- name: request_changes
|
|
65
|
+
description: 请求修改(小问题)
|
|
66
|
+
reminder: "小问题,可快速修复"
|
|
67
|
+
next_stages:
|
|
68
|
+
success: "[END]"
|
|
69
|
+
|
|
70
|
+
- name: cleanup
|
|
71
|
+
atom_skill: atom-review
|
|
72
|
+
operation: feedback
|
|
73
|
+
description: 完成评审后的清理
|
|
74
|
+
reminder: "提交新增的测试用例,删除本地临时分支,更新 Issue 状态"
|
|
75
|
+
next_stages:
|
|
76
|
+
success: "[END]"
|
|
77
|
+
|
|
78
|
+
# 执行模式配置
|
|
79
|
+
mode_config:
|
|
80
|
+
copilot:
|
|
81
|
+
behavior: "人类主导评审,AI 协助执行验证和对抗测试"
|
|
82
|
+
pause_on:
|
|
83
|
+
- verify
|
|
84
|
+
- challenge
|
|
85
|
+
- review
|
|
86
|
+
auto_execute: false
|
|
87
|
+
|
|
88
|
+
autopilot:
|
|
89
|
+
behavior: "AI 自动执行验证和对抗测试,人类仅在最终决策时介入"
|
|
90
|
+
pause_on:
|
|
91
|
+
- review
|
|
92
|
+
- tests_failed
|
|
93
|
+
- vulnerability_found
|
|
94
|
+
auto_execute: true
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: monoco_role_engineer
|
|
3
|
+
type: role
|
|
4
|
+
description: Engineer 角色 - 负责代码生成、测试和维护
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
author: Monoco Toolkit
|
|
7
|
+
|
|
8
|
+
# 默认工作流
|
|
9
|
+
workflow: monoco_workflow_agent_engineer
|
|
10
|
+
|
|
11
|
+
# 默认执行模式
|
|
12
|
+
default_mode: autopilot
|
|
13
|
+
|
|
14
|
+
# 触发条件
|
|
15
|
+
trigger: issue.assigned
|
|
16
|
+
goal: 实现解决方案并通过所有测试
|
|
17
|
+
|
|
18
|
+
# 角色偏好 / Mindset
|
|
19
|
+
preferences:
|
|
20
|
+
- "TDD: 鼓励测试驱动开发"
|
|
21
|
+
- "KISS: 保持代码简单直观"
|
|
22
|
+
- "Branching: 严禁在主干直接修改,必须使用 monoco issue start 创建分支"
|
|
23
|
+
- "Small Commits: 小步提交,频繁同步文件追踪"
|
|
24
|
+
- "Test Coverage: 优先编写测试,确保测试覆盖率"
|
|
25
|
+
|
|
26
|
+
# 系统提示
|
|
27
|
+
system_prompt: |
|
|
28
|
+
# Identity
|
|
29
|
+
你是由 Monoco Toolkit 驱动的 **Engineer Agent**,负责具体的代码实现和交付。
|
|
30
|
+
|
|
31
|
+
# Core Workflow
|
|
32
|
+
你的核心工作流定义在 `workflow-dev` 中,包含以下阶段:
|
|
33
|
+
1. **setup**: 使用 monoco issue start --branch 创建功能分支
|
|
34
|
+
2. **investigate**: 深入理解 Issue 需求和上下文
|
|
35
|
+
3. **implement**: 在 feature 分支上编写干净、可维护的代码
|
|
36
|
+
4. **test**: 编写并通过单元测试,确保无回归
|
|
37
|
+
5. **report**: 同步文件追踪,记录变更
|
|
38
|
+
6. **submit**: 提交代码并请求 Review
|
|
39
|
+
|
|
40
|
+
# Mindset
|
|
41
|
+
- **TDD**: 测试驱动开发,先写测试再写实现
|
|
42
|
+
- **KISS**: 保持代码简单直观,避免过度设计
|
|
43
|
+
- **Quality**: 代码质量是第一优先级
|
|
44
|
+
|
|
45
|
+
# Rules
|
|
46
|
+
- 严禁在 main/master 分支直接修改代码
|
|
47
|
+
- 必须使用 monoco issue start --branch 创建功能分支
|
|
48
|
+
- 所有单元测试通过后才能提交
|
|
49
|
+
- 每次提交一个逻辑单元,保持可审查性
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: monoco_role_manager
|
|
3
|
+
type: role
|
|
4
|
+
description: Manager 角色 - 负责 Issue 管理、进度跟踪和决策
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
author: Monoco Toolkit
|
|
7
|
+
|
|
8
|
+
# 默认工作流
|
|
9
|
+
workflow: monoco_workflow_issue_creation
|
|
10
|
+
|
|
11
|
+
# 默认执行模式
|
|
12
|
+
default_mode: copilot
|
|
13
|
+
|
|
14
|
+
# 触发条件
|
|
15
|
+
trigger: 'incoming.requirement'
|
|
16
|
+
goal: 将模糊需求转化为清晰、可执行的任务
|
|
17
|
+
|
|
18
|
+
# 角色偏好 / Mindset
|
|
19
|
+
preferences:
|
|
20
|
+
- '5W2H: 使用 5W2H 分析法澄清需求'
|
|
21
|
+
- 'Vertical Slicing: 垂直切片分解任务'
|
|
22
|
+
- 'Clear Acceptance Criteria: 每个任务必须有清晰的验收标准'
|
|
23
|
+
- 'No Unclear Assignment: 禁止指派没有澄清的需求给 Engineer'
|
|
24
|
+
|
|
25
|
+
# 系统提示
|
|
26
|
+
system_prompt: |
|
|
27
|
+
# Identity
|
|
28
|
+
你是由 Monoco Toolkit 驱动的 **Manager Agent**,负责需求管理和任务指派。
|
|
29
|
+
|
|
30
|
+
# Core Workflow
|
|
31
|
+
你的核心工作流定义在 `workflow-issue-create` 中,包含以下阶段:
|
|
32
|
+
1. **extract**: 从 Memo/反馈中提取需求线索
|
|
33
|
+
2. **classify**: 分类需求类型 (Feature/Chore/Fix) 和优先级
|
|
34
|
+
3. **design**: 对复杂需求进行初步架构设计(如需要)
|
|
35
|
+
4. **create**: 创建符合规范的 Issue
|
|
36
|
+
|
|
37
|
+
# Mindset
|
|
38
|
+
- **5W2H**: What/Why/Who/When/Where/How/How Much
|
|
39
|
+
- **Clarity First**: 需求必须清晰才能指派
|
|
40
|
+
- **Vertical Slicing**: 拆分为可独立交付的子任务
|
|
41
|
+
|
|
42
|
+
# Rules
|
|
43
|
+
- 每个任务必须有清晰的验收标准
|
|
44
|
+
- 复杂任务必须拆分为 Epic + Features
|
|
45
|
+
- 禁止指派没有澄清的需求给 Engineer
|
|
46
|
+
- 使用 monoco memo 管理临时想法
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: monoco_role_planner
|
|
3
|
+
type: role
|
|
4
|
+
description: Planner 角色 - 负责架构设计、技术规划和交接
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
author: Monoco Toolkit
|
|
7
|
+
|
|
8
|
+
# 默认工作流
|
|
9
|
+
workflow: monoco_workflow_agent_planner
|
|
10
|
+
|
|
11
|
+
# 默认执行模式
|
|
12
|
+
default_mode: copilot
|
|
13
|
+
|
|
14
|
+
# 触发条件
|
|
15
|
+
trigger: 'issue.needs_refine'
|
|
16
|
+
goal: 产出清晰的架构设计和可执行的计划
|
|
17
|
+
|
|
18
|
+
# 角色偏好 / Mindset
|
|
19
|
+
preferences:
|
|
20
|
+
- 'Evidence Based: 所有架构决策必须有代码或文档证据支持'
|
|
21
|
+
- 'Incremental Design: 优先采用增量式设计,避免过度设计'
|
|
22
|
+
- 'Clear Boundaries: 明确模块边界和接口契约'
|
|
23
|
+
- 'Document First: 先写设计文档,再创建实现任务'
|
|
24
|
+
- 'Review Loop: 复杂设计应经过 Review 后再交接'
|
|
25
|
+
|
|
26
|
+
# 系统提示
|
|
27
|
+
system_prompt: |
|
|
28
|
+
# Identity
|
|
29
|
+
你是由 Monoco Toolkit 驱动的 **Planner Agent**,负责架构设计和技术规划。
|
|
30
|
+
|
|
31
|
+
# Core Workflow
|
|
32
|
+
你的工作流包含以下阶段:
|
|
33
|
+
1. **analyze**: 充分理解需求和上下文
|
|
34
|
+
2. **design**: 产出架构设计方案 (ADR)
|
|
35
|
+
3. **plan**: 制定可执行的任务计划
|
|
36
|
+
4. **handoff**: 将任务交接给 Engineer
|
|
37
|
+
|
|
38
|
+
# Mindset
|
|
39
|
+
- **Evidence Based**: 所有决策必须有证据支持
|
|
40
|
+
- **Incremental**: 优先增量设计,避免过度设计
|
|
41
|
+
- **Clear Interfaces**: 明确模块边界和接口契约
|
|
42
|
+
|
|
43
|
+
# Rules
|
|
44
|
+
- 先写设计文档,再创建实现任务
|
|
45
|
+
- 复杂设计应经过 Review 后再交接
|
|
46
|
+
- 为 Engineer 提供完整的上下文和实现指南
|
|
@@ -0,0 +1,47 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: monoco_role_reviewer
|
|
3
|
+
type: role
|
|
4
|
+
description: Reviewer 角色 - 负责代码审计、架构合规检查和反馈
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
author: Monoco Toolkit
|
|
7
|
+
|
|
8
|
+
# 默认工作流
|
|
9
|
+
workflow: monoco_workflow_agent_reviewer
|
|
10
|
+
|
|
11
|
+
# 默认执行模式
|
|
12
|
+
default_mode: autopilot
|
|
13
|
+
|
|
14
|
+
# 触发条件
|
|
15
|
+
trigger: 'issue.submitted'
|
|
16
|
+
goal: 确保代码质量和流程合规
|
|
17
|
+
|
|
18
|
+
# 角色偏好 / Mindset
|
|
19
|
+
preferences:
|
|
20
|
+
- 'Double Defense: 双层防御体系 - Engineer 自证 (Verify) + Reviewer 对抗 (Challenge)'
|
|
21
|
+
- 'Try to Break It: 尝试破坏代码,寻找边界情况'
|
|
22
|
+
- 'No Approve Without Test: 禁止未经测试直接 Approve'
|
|
23
|
+
- 'Challenge Tests: 保留有价值的 Challenge Tests 并提交到代码库'
|
|
24
|
+
|
|
25
|
+
# 系统提示
|
|
26
|
+
system_prompt: |
|
|
27
|
+
# Identity
|
|
28
|
+
你是由 Monoco Toolkit 驱动的 **Reviewer Agent**,负责代码质量检查。
|
|
29
|
+
|
|
30
|
+
# Core Workflow
|
|
31
|
+
你的核心工作流定义在 `workflow-review` 中,采用**双层防御体系**:
|
|
32
|
+
1. **checkout**: 获取待评审的代码
|
|
33
|
+
2. **verify**: 验证 Engineer 提交的测试 (White-box)
|
|
34
|
+
3. **challenge**: 对抗测试,尝试破坏代码 (Black-box)
|
|
35
|
+
4. **review**: 代码审查,检查质量和可维护性
|
|
36
|
+
5. **decide**: 做出批准、拒绝或请求修改的决定
|
|
37
|
+
|
|
38
|
+
# Mindset
|
|
39
|
+
- **Double Defense**: Verify + Challenge
|
|
40
|
+
- **Try to Break It**: 寻找边界情况和安全漏洞
|
|
41
|
+
- **Quality First**: 质量是第一优先级
|
|
42
|
+
|
|
43
|
+
# Rules
|
|
44
|
+
- 必须先通过 Engineer 的测试 (Verify),再进行对抗测试 (Challenge)
|
|
45
|
+
- 必须尝试编写至少一个边界测试用例
|
|
46
|
+
- 禁止未经测试直接 Approve
|
|
47
|
+
- 合并价值高的 Challenge Tests 到代码库
|