PyPI - monoco-toolkit - Versions diffs - 0.3.11__py3-none-any.whl → 0.4.0__py3-none-any.whl - Mend

monoco-toolkit 0.3.11py3-none-any.whl → 0.4.0py3-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.

Files changed (132) hide show

monoco/core/automation/__init__.py +40 -0
monoco/core/automation/field_watcher.py +296 -0
monoco/core/automation/handlers.py +805 -0
monoco/core/config.py +29 -11
monoco/core/daemon/__init__.py +5 -0
monoco/core/daemon/pid.py +290 -0
monoco/core/git.py +15 -0
monoco/core/hooks/context.py +74 -13
monoco/core/injection.py +86 -8
monoco/core/integrations.py +0 -24
monoco/core/router/__init__.py +17 -0
monoco/core/router/action.py +202 -0
monoco/core/scheduler/__init__.py +63 -0
monoco/core/scheduler/base.py +152 -0
monoco/core/scheduler/engines.py +175 -0
monoco/core/scheduler/events.py +197 -0
monoco/core/scheduler/local.py +377 -0
monoco/core/setup.py +9 -0
monoco/core/sync.py +199 -4
monoco/core/watcher/__init__.py +63 -0
monoco/core/watcher/base.py +382 -0
monoco/core/watcher/dropzone.py +152 -0
monoco/core/watcher/im.py +460 -0
monoco/core/watcher/issue.py +303 -0
monoco/core/watcher/memo.py +192 -0
monoco/core/watcher/task.py +238 -0
monoco/daemon/app.py +3 -60
monoco/daemon/commands.py +459 -25
monoco/daemon/events.py +34 -0
monoco/daemon/scheduler.py +157 -201
monoco/daemon/services.py +42 -243
monoco/features/agent/__init__.py +25 -7
monoco/features/agent/cli.py +91 -57
monoco/features/agent/engines.py +31 -170
monoco/features/agent/resources/en/AGENTS.md +14 -14
monoco/features/agent/resources/en/skills/monoco_role_engineer/SKILL.md +101 -0
monoco/features/agent/resources/en/skills/monoco_role_manager/SKILL.md +95 -0
monoco/features/agent/resources/en/skills/monoco_role_planner/SKILL.md +177 -0
monoco/features/agent/resources/en/skills/monoco_role_reviewer/SKILL.md +139 -0
monoco/features/agent/resources/zh/skills/monoco_role_engineer/SKILL.md +101 -0
monoco/features/agent/resources/zh/skills/monoco_role_manager/SKILL.md +95 -0
monoco/features/agent/resources/zh/skills/monoco_role_planner/SKILL.md +177 -0
monoco/features/agent/resources/zh/skills/monoco_role_reviewer/SKILL.md +139 -0
monoco/features/agent/worker.py +1 -1
monoco/features/hooks/__init__.py +61 -6
monoco/features/hooks/commands.py +281 -271
monoco/features/hooks/dispatchers/__init__.py +23 -0
monoco/features/hooks/dispatchers/agent_dispatcher.py +486 -0
monoco/features/hooks/dispatchers/git_dispatcher.py +478 -0
monoco/features/hooks/manager.py +357 -0
monoco/features/hooks/models.py +262 -0
monoco/features/hooks/parser.py +322 -0
monoco/features/hooks/universal_interceptor.py +503 -0
monoco/features/im/__init__.py +67 -0
monoco/features/im/core.py +782 -0
monoco/features/im/models.py +311 -0
monoco/features/issue/commands.py +133 -60
monoco/features/issue/core.py +385 -40
monoco/features/issue/domain_commands.py +0 -19
monoco/features/issue/resources/en/AGENTS.md +17 -122
monoco/features/issue/resources/hooks/agent/before-tool.sh +102 -0
monoco/features/issue/resources/hooks/agent/session-start.sh +88 -0
monoco/features/issue/resources/hooks/{post-checkout.sh → git/git-post-checkout.sh} +10 -9
monoco/features/issue/resources/hooks/git/git-pre-commit.sh +31 -0
monoco/features/issue/resources/hooks/{pre-push.sh → git/git-pre-push.sh} +7 -13
monoco/features/issue/resources/zh/AGENTS.md +18 -123
monoco/features/memo/cli.py +15 -64
monoco/features/memo/core.py +6 -34
monoco/features/memo/models.py +24 -15
monoco/features/memo/resources/en/AGENTS.md +31 -0
monoco/features/memo/resources/zh/AGENTS.md +28 -5
monoco/features/spike/commands.py +5 -3
monoco/main.py +5 -3
{monoco_toolkit-0.3.11.dist-info → monoco_toolkit-0.4.0.dist-info}/METADATA +1 -1
monoco_toolkit-0.4.0.dist-info/RECORD +170 -0
monoco/core/execution.py +0 -67
monoco/features/agent/apoptosis.py +0 -44
monoco/features/agent/manager.py +0 -127
monoco/features/agent/resources/atoms/atom-code-dev.yaml +0 -61
monoco/features/agent/resources/atoms/atom-issue-lifecycle.yaml +0 -73
monoco/features/agent/resources/atoms/atom-knowledge.yaml +0 -55
monoco/features/agent/resources/atoms/atom-review.yaml +0 -60
monoco/features/agent/resources/en/skills/monoco_atom_core/SKILL.md +0 -99
monoco/features/agent/resources/en/skills/monoco_workflow_agent_engineer/SKILL.md +0 -94
monoco/features/agent/resources/en/skills/monoco_workflow_agent_manager/SKILL.md +0 -93
monoco/features/agent/resources/en/skills/monoco_workflow_agent_planner/SKILL.md +0 -85
monoco/features/agent/resources/en/skills/monoco_workflow_agent_reviewer/SKILL.md +0 -114
monoco/features/agent/resources/workflows/workflow-dev.yaml +0 -83
monoco/features/agent/resources/workflows/workflow-issue-create.yaml +0 -72
monoco/features/agent/resources/workflows/workflow-review.yaml +0 -94
monoco/features/agent/resources/zh/roles/monoco_role_engineer.yaml +0 -49
monoco/features/agent/resources/zh/roles/monoco_role_manager.yaml +0 -46
monoco/features/agent/resources/zh/roles/monoco_role_planner.yaml +0 -46
monoco/features/agent/resources/zh/roles/monoco_role_reviewer.yaml +0 -47
monoco/features/agent/resources/zh/skills/monoco_atom_core/SKILL.md +0 -99
monoco/features/agent/resources/zh/skills/monoco_workflow_agent_engineer/SKILL.md +0 -94
monoco/features/agent/resources/zh/skills/monoco_workflow_agent_manager/SKILL.md +0 -88
monoco/features/agent/resources/zh/skills/monoco_workflow_agent_planner/SKILL.md +0 -259
monoco/features/agent/resources/zh/skills/monoco_workflow_agent_reviewer/SKILL.md +0 -137
monoco/features/agent/session.py +0 -169
monoco/features/artifact/resources/zh/skills/monoco_atom_artifact/SKILL.md +0 -278
monoco/features/glossary/resources/en/skills/monoco_atom_glossary/SKILL.md +0 -35
monoco/features/glossary/resources/zh/skills/monoco_atom_glossary/SKILL.md +0 -35
monoco/features/hooks/adapter.py +0 -67
monoco/features/hooks/core.py +0 -441
monoco/features/i18n/resources/en/skills/monoco_atom_i18n/SKILL.md +0 -96
monoco/features/i18n/resources/en/skills/monoco_workflow_i18n_scan/SKILL.md +0 -105
monoco/features/i18n/resources/zh/skills/monoco_atom_i18n/SKILL.md +0 -96
monoco/features/i18n/resources/zh/skills/monoco_workflow_i18n_scan/SKILL.md +0 -105
monoco/features/issue/resources/en/skills/monoco_atom_issue/SKILL.md +0 -165
monoco/features/issue/resources/en/skills/monoco_workflow_issue_creation/SKILL.md +0 -167
monoco/features/issue/resources/en/skills/monoco_workflow_issue_development/SKILL.md +0 -224
monoco/features/issue/resources/en/skills/monoco_workflow_issue_management/SKILL.md +0 -159
monoco/features/issue/resources/en/skills/monoco_workflow_issue_refinement/SKILL.md +0 -203
monoco/features/issue/resources/hooks/pre-commit.sh +0 -41
monoco/features/issue/resources/zh/skills/monoco_atom_issue_lifecycle/SKILL.md +0 -190
monoco/features/issue/resources/zh/skills/monoco_workflow_issue_creation/SKILL.md +0 -167
monoco/features/issue/resources/zh/skills/monoco_workflow_issue_development/SKILL.md +0 -224
monoco/features/issue/resources/zh/skills/monoco_workflow_issue_management/SKILL.md +0 -159
monoco/features/issue/resources/zh/skills/monoco_workflow_issue_refinement/SKILL.md +0 -203
monoco/features/memo/resources/en/skills/monoco_atom_memo/SKILL.md +0 -77
monoco/features/memo/resources/en/skills/monoco_workflow_note_processing/SKILL.md +0 -140
monoco/features/memo/resources/zh/skills/monoco_atom_memo/SKILL.md +0 -77
monoco/features/memo/resources/zh/skills/monoco_workflow_note_processing/SKILL.md +0 -140
monoco/features/spike/resources/en/skills/monoco_atom_spike/SKILL.md +0 -76
monoco/features/spike/resources/en/skills/monoco_workflow_research/SKILL.md +0 -121
monoco/features/spike/resources/zh/skills/monoco_atom_spike/SKILL.md +0 -76
monoco/features/spike/resources/zh/skills/monoco_workflow_research/SKILL.md +0 -121
monoco_toolkit-0.3.11.dist-info/RECORD +0 -181
{monoco_toolkit-0.3.11.dist-info → monoco_toolkit-0.4.0.dist-info}/WHEEL +0 -0
{monoco_toolkit-0.3.11.dist-info → monoco_toolkit-0.4.0.dist-info}/entry_points.txt +0 -0
{monoco_toolkit-0.3.11.dist-info → monoco_toolkit-0.4.0.dist-info}/licenses/LICENSE +0 -0

monoco/features/issue/resources/en/skills/monoco_workflow_issue_development/SKILL.md DELETED Viewed

@@ -1,224 +0,0 @@
----
-name: monoco_workflow_issue_development
-description: Execute complete workflow for Issue development, testing, submission and review (Copilot Mode)
-type: workflow
-domain: issue
-version: 1.0.0
----
-# Issue Develop Workflow
-Complete standardized workflow for Issue development, testing, submission, review and merge.
-**Applicable Scenario**: Copilot Mode (Human-led, AI-assisted)
-**Target Users**: Developers responsible for implementing features or fixing bugs
-## Workflow State Machine
-```mermaid
-stateDiagram-v2
-    [*] --> Setup: Start Development
-    Setup --> Develop: Environment Ready
-    Setup --> Setup: Dependencies Not Met<br/>(Wait for Resolution)
-    Develop --> Test: Coding Complete
-    Develop --> Develop: Needs Iteration<br/>(Continue Development)
-    Test --> Submit: Tests Pass
-    Test --> Develop: Tests Fail<br/>(Fix Code)
-    state "Review Loop" as ReviewLoop {
-        Submit --> Review: Submit for Review
-        Review --> Fix: Changes Required
-        Fix --> Submit: Resubmit
-    }
-    Review --> Merge: Review Passed
-    Merge --> [*]: Merge Complete
-```
-## Execution Steps
-### 1. Setup
-- **Goal**: Prepare development environment, ensure ready to code
-- **Checkpoints**:
-  - [ ] Run `monoco issue start <ID> --branch` to create feature branch
-  - [ ] Confirm branch is created and switched
-  - [ ] Verify not currently on main/master branch
-  - [ ] Check if dependency Issues are completed
-  - [ ] Confirm Issue is refined (has technical task list)
-**Environment Checklist**:
-| Check Item | Command/Method |
-|------------|----------------|
-| Current Branch | `git branch --show-current` |
-| Branch Status | `git status` |
-| Dependency Issues | `monoco issue show <ID>` |
-| Code Standards | Check project lint configuration |
-### 2. Develop
-- **Goal**: Implement feature or fix bug
-- **Strategy**: Iterative development, small commits
-- **Checkpoints**:
-  - [ ] Follow project code standards
-  - [ ] Write/update unit tests
-  - [ ] Commit code regularly (small commits)
-  - [ ] Update file tracking (`monoco issue sync-files`)
-  - [ ] Maintain code reviewability (single commit < 400 lines)
-**Development Principles**:
-| Principle | Description |
-|-----------|-------------|
-| Small Commits | Each commit is a logical unit |
-| Test First | Prioritize writing test cases |
-| Continuous Sync | Update file tracking promptly |
-| Stay Focused | Avoid unrelated changes |
-### 3. Test
-- **Goal**: Ensure code quality and functional correctness
-- **Checkpoints**:
-  - [ ] Run unit tests, ensure they pass
-  - [ ] Run integration tests (if applicable)
-  - [ ] Run code style checks (lint)
-  - [ ] Manually verify functionality (if needed)
-  - [ ] Check test coverage
-**Test Levels**:
-```
-Unit Test → Integration Test → E2E Test → Manual Verification
-   ↑          ↑            ↑            ↑
- Required   Recommended   As Needed    As Needed
-```
-### 4. Submit
-- **Goal**: Prepare for code review
-- **Checkpoints**:
-  - [ ] Run `monoco issue lint` to check compliance
-  - [ ] Fix all Lint errors
-  - [ ] Update task list status (mark completed items)
-  - [ ] Write clear commit message
-  - [ ] Run `monoco issue submit <ID>`
-**Commit Message Specification**:
-```
-<type>(<scope>): <subject>
-<body>
-Refs: <ISSUE-ID>
-```
-| Type | Purpose |
-|------|---------|
-| feat | New feature |
-| fix | Bug fix |
-| docs | Documentation update |
-| style | Code formatting |
-| refactor | Refactoring |
-| test | Test related |
-| chore | Build/tools |
-### 5. Review
-- **Goal**: Code quality and process compliance check
-- **Checkpoints**:
-  - [ ] Is functionality correctly implemented
-  - [ ] Does code meet design specifications
-  - [ ] Are tests sufficient
-  - [ ] Is documentation updated
-  - [ ] Does it follow project standards
-**Review Dimensions**:
-| Dimension | Check Content |
-|-----------|---------------|
-| Correctness | Does functionality work as expected |
-| Design | Does it meet architecture design |
-| Testing | Is test coverage sufficient |
-| Standards | Does it follow code standards |
-| Documentation | Is documentation updated |
-| Performance | Are there obvious performance issues |
-| Security | Are there security risks |
-### 6. Merge
-- **Goal**: Complete Issue, merge code
-- **Checkpoints**:
-  - [ ] Code has passed review
-  - [ ] All CI checks pass
-  - [ ] Code is merged to main branch
-  - [ ] Run `monoco issue close <ID> --solution completed --prune`
-  - [ ] Verify branch is cleaned up
-  - [ ] Update Review Comments (record review feedback)
-## Decision Branches
-| Condition | Action |
-|-----------|--------|
-| Dependency Issues not completed | Return to Setup, wait for dependencies |
-| Tests fail | Return to Develop, fix code |
-| Lint fails | Fix compliance issues, resubmit |
-| Review requires changes | Return to Fix, modify per feedback |
-| Review passed | Enter Merge, merge and cleanup |
-## Compliance Requirements
-- **Prohibited**: Directly modify code on main/master branch
-- **Required**: Use `monoco issue start --branch` to create feature branch
-- **Required**: All unit tests must pass before Submit
-- **Required**: Each Issue must have at least 2 Checkboxes
-- **Required**: Review/Done phase must include Review Comments
-- **Recommended**: Small commits, frequently sync file tracking
-## Related Commands
-```bash
-# Start development
-monoco issue start FEAT-0001 --branch
-# Sync file tracking
-monoco issue sync-files
-# Check compliance
-monoco issue lint
-# Submit for review
-monoco issue submit FEAT-0001
-# Close Issue
-monoco issue close FEAT-0001 --solution completed --prune
-```
-## Relationship with flow_engineer
-The relationship between this workflow and `flow_engineer`:
-```
-issue-develop-workflow          flow_engineer
-       │                              │
-       ├── Setup ─────────────────────┤
-       ├── Develop ←──────────────────┤ Investigate → Code → Test
-       ├── Test ──────────────────────┤
-       ├── Submit ────────────────────┤ Report → Submit
-       ├── Review ────────────────────┤
-       └── Merge ─────────────────────┤
-```
-- `issue-develop-workflow`: Focuses on Issue-level process management
-- `flow_engineer`: Focuses on specific technical process for code implementation
-During the Develop phase, developers should follow `flow_engineer`'s Investigate → Code → Test → Report → Submit process.
-## Copilot Mode Tips
-As an AI Copilot, you should:
-1. **Assist coding**: Help implement features, fix bugs
-2. **Code review**: Pre-review before submission to find potential issues
-3. **Test assistance**: Help write test cases, ensure coverage
-4. **Compliance check**: Remind developers to follow project standards
-5. **Documentation sync**: Assist in updating related documentation

monoco/features/issue/resources/en/skills/monoco_workflow_issue_management/SKILL.md DELETED Viewed

@@ -1,159 +0,0 @@
----
-name: monoco_workflow_issue_management
-description: Issue Lifecycle Workflow (Flow Skill). Defines the complete Issue management process from creation to closure, ensuring task tracking and process compliance.
-type: workflow
-domain: issue
-version: 1.0.0
----
-# Issue Lifecycle Workflow
-Standardized workflow for Issue lifecycle, ensuring "Open → Start → Develop → Submit → Review → Close" process.
-## Workflow State Machine
-```mermaid
-stateDiagram-v2
-    [*] --> Open: Create Issue
-    Open --> Start: Prepare Development
-    Open --> Open: Requirements Unclear<br/>(Wait for Clarification)
-    Start --> Develop: Branch Created
-    Start --> Start: Branch Conflict<br/>(Resolve Conflict)
-    Develop --> Submit: Development Complete
-    Develop --> Develop: Tests Fail<br/>(Fix Code)
-    state "Oracle Loop" as ReviewLoop {
-        Submit --> Review: Submit for Review
-        Review --> Fix: Rejected
-        Fix --> Submit: Resubmit
-    }
-    Review --> Close: Approved for Merge
-    Close --> [*]: Cleanup Complete
-```
-## Execution Steps
-### 1. Open
-- **Goal**: Create clear, actionable Issue
-- **Input**: Requirement description, type, priority
-- **Output**: Issue Ticket file
-- **Checkpoints**:
-  - [ ] Use `monoco issue create <type> -t "Title"`
-  - [ ] Select appropriate type (epic/feature/chore/fix)
-  - [ ] Write clear description and acceptance criteria
-  - [ ] Set dependency relationships (if needed)
-  - [ ] Ensure at least 2 Checkboxes
-### 2. Start
-- **Goal**: Prepare development environment, create feature branch
-- **Checkpoints**:
-  - [ ] Run `monoco issue start <ID> --branch`
-  - [ ] Confirm branch is created and switched
-  - [ ] Verify not currently on main/master branch
-  - [ ] Check if dependency Issues are completed
-### 3. Develop
-- **Goal**: Implement feature or fix bug
-- **Strategy**: Iterative development, continuous testing
-- **Checkpoints**:
-  - [ ] Follow project code standards
-  - [ ] Write/update unit tests
-  - [ ] Run test suite, ensure it passes
-  - [ ] Commit code regularly (small commits)
-  - [ ] Update file tracking (`monoco issue sync-files`)
-### 4. Submit
-- **Goal**: Prepare for code review
-- **Checkpoints**:
-  - [ ] Run `monoco issue lint` to check compliance
-  - [ ] Fix all Lint errors
-  - [ ] Update task list status
-  - [ ] Run `monoco issue submit <ID>`
-  - [ ] Write change summary
-### 5. Review
-- **Goal**: Code quality and process compliance check
-- **Checkpoints**:
-  - [ ] Is functionality correctly implemented
-  - [ ] Does code meet design specifications
-  - [ ] Are tests sufficient
-  - [ ] Is documentation updated
-  - [ ] Does it follow project standards
-### 6. Close
-- **Goal**: Complete Issue, cleanup environment
-- **Checkpoints**:
-  - [ ] Code is merged to main branch
-  - [ ] Run `monoco issue close <ID> --solution completed --prune`
-  - [ ] Verify branch is cleaned up
-  - [ ] Update Review Comments (if needed)
-## Decision Branches
-| Condition | Action |
-|-----------|--------|
-| Requirements unclear | Return to Open, request clarification |
-| Branch creation fails | Check Git status, resolve conflicts |
-| Tests fail | Return to Develop, fix code |
-| Lint fails | Fix compliance issues, resubmit |
-| Review rejected | Return to Develop, modify per feedback |
-| Review passed | Enter Close, merge and cleanup |
-## Compliance Requirements
-- **Prohibited**: Directly modify code on main/master branch
-- **Required**: Use `monoco issue start --branch` to create feature branch
-- **Required**: All unit tests must pass before Submit
-- **Required**: Each Issue must have at least 2 Checkboxes
-- **Required**: Review/Done phase must include Review Comments
-- **Recommended**: Small commits, frequently sync file tracking
-## Related Commands
-```bash
-# Create Issue
-monoco issue create feature -t "Title"
-# Start development
-monoco issue start FEAT-0001 --branch
-# Sync file tracking
-monoco issue sync-files
-# Check compliance
-monoco issue lint
-# Submit for review
-monoco issue submit FEAT-0001
-# Close Issue
-monoco issue close FEAT-0001 --solution completed --prune
-```
-## Issue Type Guide
-| Type | Purpose | Prefix | Mindset |
-|------|---------|--------|---------|
-| Epic | Grand goals, vision container | EPIC- | Architect |
-| Feature | User value increment | FEAT- | Product Owner |
-| Chore | Engineering tasks | CHORE- | Builder |
-| Fix | Bug fixes | FIX- | Debugger |
-## Relationship with flow_engineer
-This workflow complements `flow_engineer`:
-- `issue-lifecycle-workflow`: Focuses on Issue management process
-- `flow_engineer`: Focuses on code implementation process
-Engineers should follow `flow_engineer`'s Investigate → Code → Test → Report → Submit process during the Develop phase.

monoco/features/issue/resources/en/skills/monoco_workflow_issue_refinement/SKILL.md DELETED Viewed

@@ -1,203 +0,0 @@
----
-name: monoco_workflow_issue_refinement
-description: Investigate and refine Issue, supplement technical details and implementation plan (Copilot Mode)
-type: workflow
-domain: issue
-version: 1.0.0
----
-# Issue Refine Workflow
-Standardized workflow for technical investigation, architecture analysis and solution design for newly created or pending refinement Issues.
-**Applicable Scenario**: Copilot Mode (Human-led, AI-assisted)
-**Target Users**: Developers who need to deeply understand problems and formulate implementation plans
-## Workflow State Machine
-```mermaid
-stateDiagram-v2
-    [*] --> Investigate: Start Refinement
-    Investigate --> Analyze: Gather Information
-    Investigate --> Investigate: Insufficient Information<br/>(Continue Investigation)
-    Analyze --> Architect: Architecture Design Required
-    Analyze --> Document: Direct Documentation
-    Architect --> Document: Design Complete
-    Document --> [*]: Issue Refinement Complete
-```
-## Execution Steps
-### 1. Investigate
-- **Goal**: Comprehensively gather information related to the Issue
-- **Input**: Issue Ticket, related code, documentation
-- **Output**: Information gathering report
-- **Checkpoints**:
-  - [ ] Read Issue description, understand core problem
-  - [ ] Identify related code modules and files
-  - [ ] Review related Issue/PR history
-  - [ ] Check external dependencies and constraints
-  - [ ] Collect similar implementation references (Spike)
-**Investigation Dimensions**:
-| Dimension | Investigation Content |
-|-----------|----------------------|
-| Code | Current implementation of related modules |
-| History | Related Issues, PRs, design documents |
-| Dependencies | External libraries, APIs, service dependencies |
-| Constraints | Performance requirements, security requirements, compatibility |
-| References | Best practices for similar features |
-### 2. Analyze
-- **Goal**: Analyze gathered information, identify key problems and solution options
-- **Checkpoints**:
-  - [ ] Analyze architecture inheritance (how to fit into existing architecture)
-  - [ ] Assess security impact
-  - [ ] Assess performance impact
-  - [ ] Assess maintainability
-  - [ ] Identify potential risks and mitigation measures
-**Analysis Framework**:
-#### Architecture Inheritance
-- Are existing architecture patterns applicable?
-- Is a new abstraction layer needed?
-- Impact on coupling with existing modules?
-#### Security Assessment
-- Input validation requirements
-- Access control requirements
-- Data protection requirements
-- Potential attack surface analysis
-#### Performance Assessment
-- Time complexity impact
-- Space complexity impact
-- Concurrency/parallelism requirements
-- Resource usage estimation
-#### Maintainability Assessment
-- Code complexity changes
-- Test coverage requirements
-- Documentation update requirements
-- Future extensibility
-### 3. Architect (Optional)
-- **Goal**: Architecture design for complex Issues
-- **Applicable**: Issues involving architecture changes or large features
-- **Checkpoints**:
-  - [ ] Determine technical solution selection
-  - [ ] Design interfaces and interaction protocols
-  - [ ] Plan data model changes
-  - [ ] Define implementation milestones
-**Outputs**:
-- Architecture Decision Record (ADR)
-- Interface design document
-- Data model changes
-- Milestone plan
-### 4. Document
-- **Goal**: Update analysis results to Issue
-- **Checkpoints**:
-  - [ ] Update technical task list
-  - [ ] Add architecture decision explanation
-  - [ ] Supplement risks and mitigation measures
-  - [ ] Update acceptance criteria (if needed)
-  - [ ] Add reference links and dependency descriptions
-  - [ ] Run `monoco issue lint` to verify compliance
-**Refined Issue Structure**:
-```markdown
-## Objective
-[Original Content]
-## Acceptance Criteria
-- [ ] Acceptance criterion 1
-- [ ] Acceptance criterion 2
-## Technical Analysis
-### Current State Analysis
-Describe current code state and related implementation.
-### Solution Selection
-| Solution | Pros | Cons | Decision |
-|----------|------|------|----------|
-| A | ... | ... | Adopted/Alternative |
-| B | ... | ... | Alternative/Abandoned |
-### Risk Assessment
-| Risk | Impact | Mitigation |
-|------|--------|------------|
-| Risk1 | High/Medium/Low | Measure... |
-## Technical Tasks
-- [ ] Task 1
-- [ ] Task 2
-## References
-- Related Issue: #XXX
-- Reference Implementation: [Link]
-- ADR: [Link]
-```
-## Decision Branches
-| Condition | Action |
-|-----------|--------|
-| Insufficient information | Return to Investigate, continue gathering |
-| Architecture design needed | Enter Architect phase |
-| Solution is clear | Directly enter Document phase |
-| Blocking dependency found | Create dependency Issue, mark current Issue |
-| Problem too complex | Suggest splitting into multiple Issues |
-## Refinement Level Guide
-| Issue Type | Refinement Requirements |
-|------------|------------------------|
-| Epic | Must include architecture design, milestones, subtask decomposition |
-| Feature | Must include technical solution, risk assessment, task decomposition |
-| Chore | Must include implementation steps, impact scope |
-| Fix | Must include root cause analysis, fix solution, test cases |
-## Related Commands
-```bash
-# View Issue details
-monoco issue show <ID>
-# Check compliance
-monoco issue lint
-# Sync file tracking
-monoco issue sync-files
-# View related Spike
-monoco spike list
-```
-## Relationship with flow_engineer
-This workflow complements `flow_engineer`:
-- `issue-refine-workflow`: Focuses on Issue refinement phase, completing technical investigation before development
-- `flow_engineer`: Focuses on code implementation phase, executing Investigate → Code → Test → Report → Submit
-Information gathered during refinement phase will provide important input for the Engineer phase's Investigate.
-## Copilot Mode Tips
-As an AI Copilot, you should:
-1. **Explore proactively**: Help developers discover potential issues and edge cases
-2. **Provide comparisons**: Give multiple technical solutions, analyze pros and cons
-3. **Assist evaluation**: Help with security, performance impact assessment
-4. **Remind omissions**: Check for missing key information or risk points

monoco/features/issue/resources/hooks/pre-commit.sh DELETED Viewed

@@ -1,41 +0,0 @@
-#!/bin/sh
-# Issue Feature Pre-Commit Hook
-# Runs monoco issue lint on staged Issue files
-echo "[Monoco] Checking Issue integrity..."
-# Get the list of staged Issue files
-STAGED_ISSUES=$(git diff --cached --name-only --diff-filter=ACM | grep -E '^Issues/.*\.md$' || true)
-if [ -z "$STAGED_ISSUES" ]; then
-    echo "[Monoco] No Issue files staged. Skipping lint."
-    exit 0
-fi
-# Run lint on staged Issue files
-echo "[Monoco] Running lint on staged Issue files..."
-# Build file list for monoco command
-FILE_ARGS=""
-for file in $STAGED_ISSUES; do
-    FILE_ARGS="$FILE_ARGS $file"
-done
-# Execute lint on each file
-LINT_EXIT=0
-for file in $STAGED_ISSUES; do
-    $MONOCO_CMD issue lint "$file"
-    if [ $? -ne 0 ]; then
-        LINT_EXIT=1
-    fi
-done
-if [ $LINT_EXIT -ne 0 ]; then
-    echo ""
-    echo "[Monoco] Issue lint failed. Please fix the errors above."
-    echo "[Monoco] You can run 'monoco issue lint --fix' to attempt automatic fixes."
-    exit $LINT_EXIT
-fi
-echo "[Monoco] Issue lint passed."
-exit 0

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

monoco-toolkit 0.3.11py3-none-any.whl → 0.4.0py3-none-any.whl