monoco-toolkit 0.3.12__py3-none-any.whl → 0.4.0__py3-none-any.whl

monoco/features/agent/resources/atoms/atom-issue-lifecycle.yaml

@@ -1,73 +0,0 @@
----
-name: atom-issue-lifecycle
-type: atom
-domain: issue
-description: Issue 生命周期管理的原子操作 - 创建、启动、提交、关闭工作单元
-version: 1.0.0
-author: Monoco Toolkit
-
-# 系统级合规规则（定义一次，全局生效）
-compliance_rules:
-  - rule: "禁止在 main/master 分支直接修改代码"
-    severity: error
-    check: "git branch --show-current"
-    fail_if: "main|master"
-  
-  - rule: "必须使用 feature 分支进行开发"
-    severity: error
-    command: "monoco issue start <ID> --branch"
-  
-  - rule: "提交前必须通过 lint 检查"
-    severity: error
-    command: "monoco issue lint"
-  
-  - rule: "每个 Issue 必须至少包含 2 个 Checkbox"
-    severity: error
-    check: "checkbox_count >= 2"
-  
-  - rule: "Review/Done 阶段必须包含 Review Comments"
-    severity: warning
-    check: "review_comments_section exists"
-
-# 原子操作定义
-operations:
-  - name: create
-    description: 创建新的 Issue 工作单元
-    command: "monoco issue create <type> -t <title>"
-    reminder: "选择合适的类型 (epic/feature/chore/fix)，编写清晰的描述"
-    checkpoints:
-      - "必须包含至少 2 个 Checkbox"
-      - "标题必须与 Front Matter 一致"
-  
-  - name: start
-    description: 启动开发，创建功能分支
-    command: "monoco issue start <ID> --branch"
-    reminder: "确保使用 --branch 创建功能分支，禁止在 main/master 上开发"
-    checkpoints:
-      - "禁止在 main/master 分支直接修改代码"
-      - "必须创建 feature 分支"
-  
-  - name: sync
-    description: 同步文件追踪，记录修改的文件
-    command: "monoco issue sync-files"
-    reminder: "定期同步文件追踪，保持 Issue 与代码变更同步"
-  
-  - name: lint
-    description: 检查 Issue 合规性
-    command: "monoco issue lint"
-    reminder: "提交前必须运行 lint 检查"
-    checkpoints:
-      - "必须通过所有合规检查"
-  
-  - name: submit
-    description: 提交代码进行评审
-    command: "monoco issue submit <ID>"
-    reminder: "确保所有测试通过，lint 无错误后再提交"
-    checkpoints:
-      - "所有单元测试必须通过"
-      - "必须通过 lint 检查"
-  
-  - name: close
-    description: 关闭 Issue，清理环境
-    command: "monoco issue close <ID> --solution completed --prune"
-    reminder: "代码合并后及时关闭 Issue，清理 feature 分支"

monoco/features/agent/resources/atoms/atom-knowledge.yaml

@@ -1,55 +0,0 @@
----
-name: atom-knowledge
-type: atom
-domain: knowledge
-description: 知识管理的原子操作 - 捕获、处理、转化、归档
-version: 1.0.0
-author: Monoco Toolkit
-
-# 系统级合规规则
-compliance_rules:
-  - rule: "Memo 是临时的，不应无限堆积"
-    severity: warning
-  
-  - rule: "可执行的想法必须转为 Issue 追踪"
-    severity: error
-
-# 原子操作定义
-operations:
-  - name: capture
-    description: 快速捕获 fleeting ideas
-    command: "monoco memo add <content>"
-    reminder: "保持简洁，不中断当前工作流，添加上下文"
-    checkpoints:
-      - "使用简洁的描述"
-      - "添加上下文（-c file:line 如适用）"
-      - "不中断当前任务流"
-  
-  - name: process
-    description: 定期处理 Memo，评估价值
-    command: "monoco memo list"
-    reminder: "定期回顾和分类 Memo（建议每周）"
-    checkpoints:
-      - "运行 monoco memo list 查看所有 Memo"
-      - "评估每个 Memo 的价值"
-      - "分类：可执行 / 纯参考 / 无价值"
-  
-  - name: convert
-    description: 将可执行的 Memo 转化为 Issue
-    command: "monoco issue create <type> -t <title>"
-    reminder: "有价值的想法尽快转为 Issue"
-    checkpoints:
-      - "判断 Issue 类型 (feature/chore/fix)"
-      - "编写清晰的描述和验收标准"
-      - "关联原始 Memo"
-    compliance_rules:
-      - rule: "可执行的想法必须转为 Issue 追踪"
-        severity: error
-  
-  - name: archive
-    description: 归档纯参考资料
-    reminder: "纯参考资料归档保存，无价值的直接删除"
-    checkpoints:
-      - "确认 Memo 内容为纯参考资料"
-      - "移动到知识库或文档"
-      - "从 Memo 列表中移除"

monoco/features/agent/resources/atoms/atom-review.yaml

@@ -1,60 +0,0 @@
----
-name: atom-review
-type: atom
-domain: review
-description: 代码评审的原子操作 - 检出、验证、对抗、反馈
-version: 1.0.0
-author: Monoco Toolkit
-
-# 系统级合规规则
-compliance_rules:
-  - rule: "必须先通过 Engineer 的测试 (Verify)，再进行对抗测试 (Challenge)"
-    severity: error
-  
-  - rule: "必须尝试编写至少一个边界测试用例"
-    severity: warning
-  
-  - rule: "禁止未经测试直接 Approve"
-    severity: error
-
-# 原子操作定义
-operations:
-  - name: checkout
-    description: 检出待评审的代码
-    reminder: "获取待评审的 PR/Branch，确认与 Base 分支的差异"
-    checkpoints:
-      - "检出 PR/Branch"
-      - "确认与 Base 分支的差异"
-      - "检查环境配置"
-  
-  - name: verify
-    description: 验证 Engineer 提交的测试 (White-box)
-    reminder: "先运行 Engineer 编写的测试，验证功能正确性"
-    checkpoints:
-      - "运行 Engineer 编写的单元测试"
-      - "运行集成测试（如适用）"
-      - "检查测试覆盖率报告"
-    compliance_rules:
-      - rule: "如果现有测试失败，直接进入 Reject 流程"
-        severity: error
-  
-  - name: challenge
-    description: 对抗测试，尝试破坏代码 (Black-box / Edge Cases)
-    reminder: "Try to break it - 寻找边界情况和安全漏洞"
-    checkpoints:
-      - "分析代码逻辑，寻找盲区（并发、大/小数值、注入攻击等）"
-      - "编写新的 Challenge Test Cases"
-      - "运行这些新测试"
-    compliance_rules:
-      - rule: "必须尝试编写至少一个边界测试用例"
-        severity: warning
-  
-  - name: feedback
-    description: 提供评审反馈
-    reminder: "明确批准、拒绝或请求修改，提供具体反馈"
-    checkpoints:
-      - "功能是否正确实现"
-      - "代码是否符合设计规范"
-      - "测试是否充分"
-      - "文档是否同步更新"
-      - "是否遵循项目规范"

monoco/features/agent/resources/en/skills/monoco_atom_core/SKILL.md

@@ -1,99 +0,0 @@
----
-name: monoco_atom_core
-description: Core skill for Monoco Toolkit. Provides essential commands for project initialization, configuration, and workspace management.
-type: atom
-version: 1.0.0
----
-
-# Monoco Core
-
-Core functionality and commands for the Monoco Toolkit.
-
-## Overview
-
-Monoco is a developer productivity toolkit that provides:
-
-- **Project initialization** with standardized structure
-- **Configuration management** at global and project levels
-- **Workspace management** for multi-project setups
-
-## Key Commands
-
-### Project Setup
-
-- **`monoco init`**: Initialize a new Monoco project
-  - Creates `.monoco/` directory with default configuration
-  - Sets up project structure (Issues/, .references/, etc.)
-  - Generates initial documentation
-
-### Configuration
-
-- **`monoco config`**: Manage configuration
-  - `monoco config get <key>`: View configuration value
-  - `monoco config set <key> <value>`: Update configuration
-  - Supports both global (`~/.monoco/config.yaml`) and project (`.monoco/config.yaml`) scopes
-
-### Agent Integration
-
-- **`monoco sync`**: Synchronize with agent environments
-  - Injects system prompts into agent configuration files (GEMINI.md, CLAUDE.md, etc.)
-  - Distributes skills to agent framework directories
-  - Respects language configuration from `i18n.source_lang`
-
-- **`monoco uninstall`**: Clean up agent integrations
-  - Removes managed blocks from agent configuration files
-  - Cleans up distributed skills
-
-### Git Workflow Integration
-
-Monoco enforces a **Feature Branch Workflow** to ensure code isolation and quality:
-
-- **`monoco init`**: Automatically installs Git Hooks
-  - **pre-commit**: Runs Issue Linter and code formatting checks
-  - **pre-push**: Executes test suite and integrity validation
-  - All hooks configurable via `.monoco/config.yaml`
-
-- **Branch Isolation Strategy**:
-  - ⚠️ **Required**: Use `monoco issue start <ID> --branch` to create isolated environment
-  - Auto-generates normalized branch names: `feat/<id>-<slug>`
-  - **Main Protection**: Linter blocks direct code modifications on `main`/`master` branches
-
-- **File Tracking**: `monoco issue sync-files` auto-syncs Git changes to Issue metadata
-
-> 📖 **Detailed Workflow**: See `monoco-issue` skill for complete Issue lifecycle management guide.
-
-## Configuration Structure
-
-Configuration is stored in YAML format at:
-
-- **Global**: `~/.monoco/config.yaml`
-- **Project**: `.monoco/config.yaml`
-
-Key configuration sections:
-
-- `core`: Log level, author
-- `paths`: Directory paths (issues, spikes, specs)
-- `project`: Project metadata, spike repos, workspace members
-- `i18n`: Internationalization settings
-- `agent`: Agent framework integration settings
-
-## Best Practices
-
-### Basic Operations
-
-1. **Use CLI commands** instead of manual file editing when possible
-2. **Run `monoco sync`** after configuration changes to update agent environments
-3. **Commit `.monoco/config.yaml`** to version control for team consistency
-4. **Keep global config minimal** - most settings should be project-specific
-
-### Git Workflow (⚠️ CRITICAL for Agents)
-
-5. **Strictly follow branch isolation**:
-   - ✅ Always use: `monoco issue start <ID> --branch`
-   - ❌ Never modify code directly on `main`/`master` branches
-   - 📝 Before commit: Run `monoco issue sync-files` to update file tracking
-
-6. **Quality Gates**:
-   - Git Hooks will auto-run checks, don't bypass (`--no-verify`)
-   - Ensure `monoco issue lint` passes before committing
-   - Use `monoco issue submit` to generate delivery reports

monoco/features/agent/resources/en/skills/monoco_workflow_agent_engineer/SKILL.md

@@ -1,94 +0,0 @@
----
-name: monoco_workflow_agent_engineer
-description: Standardized workflow for the Engineer role (Flow Skill). Defines the standard operating procedure from requirement investigation to code submission, ensuring test coverage and code quality.
-type: workflow
-role: engineer
-version: 1.0.0
----
-
-# Engineer Flow
-
-Standardized workflow for the Engineer role, ensuring code development follows the "Investigate → Code → Test → Report → Submit" process.
-
-## Workflow State Machine
-
-```mermaid
-stateDiagram-v2
-    [*] --> Investigate: Receive Task
-    
-    Investigate --> Code: Requirements Clear
-    Investigate --> Investigate: Requirements Fuzzy<br/>(Request Clarification)
-    
-    Code --> Test: Coding Complete
-    
-    Test --> Test: Test Failed<br/>(Fix Code)
-    Test --> Report: Test Passed
-    
-    Report --> Submit: Report Complete
-    
-    Submit --> [*]: Submission Successful
-```
-
-## Execution Steps
-
-### 1. Investigate
-
-- **Goal**: Fully understand requirements, identify technical risks and dependencies
-- **Input**: Issue description, relevant code, dependent Issues
-- **Output**: Technical solution draft, risk checklist
-- **Checkpoints**:
-  - [ ] Read and understand Issue description
-  - [ ] Identify relevant code files
-  - [ ] Check dependent Issue status
-  - [ ] Assess technical feasibility
-
-### 2. Code
-
-- **Goal**: Implement feature or fix defect
-- **Prerequisites**: Requirements are clear, branch is created (`monoco issue start <ID> --branch`)
-- **Checkpoints**:
-  - [ ] Follow project coding standards
-  - [ ] Write/update necessary documentation
-  - [ ] Handle edge cases
-
-### 3. Test
-
-- **Goal**: Ensure code quality and functional correctness
-- **Strategy**: Loop testing until passed
-- **Checkpoints**:
-  - [ ] Write/update unit tests
-  - [ ] Run test suite (`pytest`, `cargo test`, etc.)
-  - [ ] Fix failed tests
-  - [ ] Check test coverage
-
-### 4. Report
-
-- **Goal**: Document changes, update Issue status
-- **Checkpoints**:
-  - [ ] Update Issue file tracking (`monoco issue sync-files`)
-  - [ ] Write change summary
-  - [ ] Update task checklist (Checkboxes)
-
-### 5. Submit
-
-- **Goal**: Complete code submission, enter review process
-- **Checkpoints**:
-  - [ ] Run `monoco issue lint` for compliance check
-  - [ ] Run `monoco issue submit <ID>`
-  - [ ] Wait for review results
-
-## Decision Branches
-
-| Condition | Action |
-|-----------|--------|
-| Requirements unclear | Return to Investigate, request clarification |
-| Test failed | Return to Code, fix issues |
-| Lint failed | Fix compliance issues, resubmit |
-| Review rejected | Return to Code, modify according to feedback |
-
-## Compliance Requirements
-
-- **Prohibited**: Skip tests and submit directly
-- **Prohibited**: Modify code directly on main/master branch
-- **Required**: Use `monoco issue start --branch` to create feature branch
-- **Required**: All unit tests must pass before Submit

monoco/features/agent/resources/en/skills/monoco_workflow_agent_manager/SKILL.md

@@ -1,93 +0,0 @@
----
-name: monoco_workflow_agent_manager
-description: Standardized workflow for the Manager role (Flow Skill). Defines the standard operating procedure from inbox organization to task assignment, ensuring clear requirements and reasonable task breakdown.
-type: workflow
-role: manager
-version: 1.0.0
----
-
-# Manager Flow
-
-Standardized workflow for the Manager role, focusing on inbox organization, requirement refinement, and task assignment.
-
-## Workflow State Machine
-
-```mermaid
-stateDiagram-v2
-    [*] --> Inbox: New Input
-    
-    Inbox --> Triage: Review
-    
-    Triage --> Refine: Needs Clarification
-    Triage --> Assign: Ready
-    Triage --> Archive: Not Actionable
-    
-    Refine --> Assign: Refined
-    Refine --> Refine: Still Unclear
-    
-    Assign --> [*]: Task Assigned
-    Archive --> [*]: Discarded
-```
-
-## Execution Steps
-
-### 1. Inbox (收件箱)
-
-- **Goal**: Collect all new inputs (Memos, external requests, ideas)
-- **Input**: Raw notes, meeting minutes, user feedback
-- **Checkpoints**:
-  - [ ] Run `monoco memo list` to check pending memos
-  - [ ] Review external issue trackers (if any)
-  - [ ] Collect stakeholder requests
-
-### 2. Triage (分类)
-
-- **Goal**: Quick classification of inbox items
-- **Checkpoints**:
-  - [ ] Is this actionable?
-  - [ ] Is this a bug, feature, chore, or epic?
-  - [ ] Does it need immediate attention?
-  - [ ] Is there enough context to proceed?
-
-### 3. Refine (细化)
-
-- **Goal**: Transform vague ideas into actionable requirements
-- **Checkpoints**:
-  - [ ] Clarify the "Why" (business value)
-  - [ ] Define the "What" (acceptance criteria)
-  - [ ] Identify dependencies and blockers
-  - [ ] Estimate effort (rough sizing)
-
-### 4. Assign (指派)
-
-- **Goal**: Create proper Issues and assign to team members
-- **Checkpoints**:
-  - [ ] Create Issue using `monoco issue create <type> -t "Title"`
-  - [ ] Link related Memos or Issues
-  - [ ] Set appropriate priority and labels
-  - [ ] Assign to team member (or leave unassigned for pickup)
-
-### 5. Archive (归档)
-
-- **Goal**: Clean up non-actionable items
-- **Checkpoints**:
-  - [ ] Document why it's not actionable
-  - [ ] Move to appropriate archive location
-  - [ ] Update stakeholders if needed
-
-## Decision Matrix
-
-| Input Type | Action | Next Step |
-|------------|--------|-----------|
-| Clear bug report | Create Fix Issue | Assign |
-| Vague feature idea | Needs refinement | Refine |
-| Technical debt | Create Chore Issue | Assign |
-| Strategic initiative | Create Epic | Refine |
-| Pure reference material | Archive | Archive |
-
-## Best Practices
-
-1. **Inbox Zero**: Process inbox regularly, don't let items accumulate
-2. **Clear Acceptance Criteria**: Every Issue must have verifiable acceptance criteria
-3. **Right Sizing**: Break down large tasks into manageable Issues
-4. **Context Preservation**: Always link back to original memos or requests

monoco/features/agent/resources/en/skills/monoco_workflow_agent_planner/SKILL.md

@@ -1,85 +0,0 @@
----
-name: monoco_workflow_agent_planner
-description: Standardized workflow for the Planner role (Flow Skill). Responsible for analysis, design, planning, and handoff.
-type: workflow
-role: planner
-version: 1.0.0
----
-
-# Planner Flow
-
-Standardized workflow for the Planner role, focusing on technical analysis, architecture design, and implementation planning.
-
-## Workflow State Machine
-
-```mermaid
-stateDiagram-v2
-    [*] --> Analyze: Receive Requirements
-    
-    Analyze --> Design: Requirements Understood
-    Analyze --> Analyze: Needs More Info
-    
-    Design --> Plan: Design Approved
-    Design --> Design: Design Rejected
-    
-    Plan --> Handoff: Plan Complete
-    
-    Handoff --> [*]: Ready for Implementation
-```
-
-## Execution Steps
-
-### 1. Analyze (分析)
-
-- **Goal**: Deep understanding of requirements and constraints
-- **Input**: Feature/Chore Issue, stakeholder requirements
-- **Output**: Analysis document, technical constraints list
-- **Checkpoints**:
-  - [ ] Read and understand requirements thoroughly
-  - [ ] Identify technical constraints (performance, security, compatibility)
-  - [ ] Research existing solutions and patterns
-  - [ ] Document assumptions and risks
-
-### 2. Design (设计)
-
-- **Goal**: Create technical design and architecture
-- **Checkpoints**:
-  - [ ] Define system architecture and components
-  - [ ] Design data models and interfaces
-  - [ ] Consider scalability and maintainability
-  - [ ] Document design decisions (ADR)
-
-### 3. Plan (规划)
-
-- **Goal**: Break down design into implementable tasks
-- **Checkpoints**:
-  - [ ] Create sub-tasks or child Issues
-  - [ ] Define dependencies between tasks
-  - [ ] Estimate effort for each task
-  - [ ] Identify required skills and resources
-
-### 4. Handoff (交接)
-
-- **Goal**: Prepare comprehensive handoff to Engineering
-- **Checkpoints**:
-  - [ ] Document implementation guidelines
-  - [ ] Create technical specification (if needed)
-  - [ ] Update parent Issue with plan summary
-  - [ ] Link all child Issues to parent
-
-## Output Artifacts
-
-| Artifact | Purpose | Location |
-|----------|---------|----------|
-| Analysis Notes | Document findings and constraints | Issue comments or linked doc |
-| Architecture Diagram | Visual representation of design | `docs/architecture/` or Issue |
-| ADR | Record design decisions | `docs/adr/` |
-| Task Breakdown | List of implementable sub-tasks | Child Issues |
-| Technical Spec | Detailed implementation guide | Issue description or linked doc |
-
-## Best Practices
-
-1. **Design for Change**: Anticipate future changes in your design
-2. **Prototype When Uncertain**: Build quick prototypes to validate approaches
-3. **Review Early**: Get feedback on designs before full planning
-4. **Document Trade-offs**: Always document why certain decisions were made

monoco/features/agent/resources/en/skills/monoco_workflow_agent_reviewer/SKILL.md

@@ -1,114 +0,0 @@
----
-name: monoco_workflow_agent_reviewer
-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.
-type: workflow
-role: reviewer
-version: 1.0.0
----
-
-# Reviewer Flow
-
-Standardized workflow for the Reviewer role, ensuring thorough code review and quality assurance.
-
-## Workflow State Machine
-
-```mermaid
-stateDiagram-v2
-    [*] --> Checkout: Start Review
-    
-    Checkout --> Review: Code Ready
-    
-    Review --> Test: Code Review Passed
-    Review --> Review: Issues Found<br/>(Request Changes)
-    
-    Test --> Approve: Tests Pass
-    Test --> Test: Issues Found<br/>(Report Bugs)
-    
-    Approve --> [*]: Review Complete
-```
-
-## Execution Steps
-
-### 1. Checkout (检出)
-
-- **Goal**: Set up review environment
-- **Checkpoints**:
-  - [ ] Checkout the PR branch
-  - [ ] Review Issue description and acceptance criteria
-  - [ ] Check related files and context
-  - [ ] Run `monoco issue lint` to verify compliance
-
-### 2. Review (审查)
-
-- **Goal**: Thorough code review
-- **Checkpoints**:
-  - [ ] Review code against acceptance criteria
-  - [ ] Check code style and conventions
-  - [ ] Verify error handling and edge cases
-  - [ ] Review test coverage and quality
-  - [ ] Check documentation updates
-
-### 3. Test (测试)
-
-- **Goal**: Adversarial testing and verification
-- **Checkpoints**:
-  - [ ] Run full test suite
-  - [ ] Perform manual testing if needed
-  - [ ] Test edge cases and error scenarios
-  - [ ] Verify integration points
-
-### 4. Approve (批准)
-
-- **Goal**: Complete review with decision
-- **Checkpoints**:
-  - [ ] Summarize review findings
-  - [ ] Provide constructive feedback
-  - [ ] Update Issue status if needed
-  - [ ] Record review comments in Issue
-
-## Review Checklist
-
-### Code Quality
-- [ ] Code follows project conventions
-- [ ] No obvious bugs or logic errors
-- [ ] Proper error handling
-- [ ] Adequate logging (where appropriate)
-
-### Testing
-- [ ] Unit tests cover new code
-- [ ] Integration tests pass
-- [ ] Edge cases are tested
-- [ ] No flaky tests introduced
-
-### Documentation
-- [ ] Code comments are clear and helpful
-- [ ] Public APIs are documented
-- [ ] README/docs updated if needed
-
-### Security
-- [ ] No hardcoded secrets
-- [ ] Input validation in place
-- [ ] No SQL injection or XSS vulnerabilities
-
-## Review Comments Format
-
-```markdown
-## Review Comments
-
-### [File:Line] Issue Type: Brief Description
-
-**Severity**: [blocking|major|minor|nit]
-
-**Details**: Detailed explanation of the issue
-
-**Suggestion**: How to fix or improve
-
----
-```
-
-## Best Practices
-
-1. **Be Constructive**: Focus on the code, not the person
-2. **Explain Why**: Always explain the reasoning behind suggestions
-3. **Prioritize**: Distinguish between blocking issues and nits
-4. **Respond Promptly**: Don't let reviews sit for too long