tapps-agents 3.5.39__py3-none-any.whl → 3.5.41__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.
- tapps_agents/__init__.py +2 -2
- tapps_agents/agents/enhancer/agent.py +2728 -2728
- tapps_agents/agents/implementer/agent.py +35 -13
- tapps_agents/agents/reviewer/agent.py +43 -10
- tapps_agents/agents/reviewer/scoring.py +59 -68
- tapps_agents/agents/reviewer/tools/__init__.py +24 -0
- tapps_agents/agents/reviewer/tools/ruff_grouping.py +250 -0
- tapps_agents/agents/reviewer/tools/scoped_mypy.py +284 -0
- tapps_agents/beads/__init__.py +11 -0
- tapps_agents/beads/hydration.py +213 -0
- tapps_agents/beads/specs.py +206 -0
- tapps_agents/cli/commands/health.py +19 -3
- tapps_agents/cli/commands/simple_mode.py +842 -676
- tapps_agents/cli/commands/task.py +227 -0
- tapps_agents/cli/commands/top_level.py +13 -0
- tapps_agents/cli/main.py +658 -651
- tapps_agents/cli/parsers/top_level.py +1978 -1881
- tapps_agents/core/config.py +1622 -1622
- tapps_agents/core/init_project.py +3012 -2897
- tapps_agents/epic/markdown_sync.py +105 -0
- tapps_agents/epic/orchestrator.py +1 -2
- tapps_agents/epic/parser.py +427 -423
- tapps_agents/experts/adaptive_domain_detector.py +0 -2
- tapps_agents/experts/knowledge/api-design-integration/api-security-patterns.md +15 -15
- tapps_agents/experts/knowledge/api-design-integration/external-api-integration.md +19 -44
- tapps_agents/health/checks/outcomes.backup_20260204_064058.py +324 -0
- tapps_agents/health/checks/outcomes.backup_20260204_064256.py +324 -0
- tapps_agents/health/checks/outcomes.backup_20260204_064600.py +324 -0
- tapps_agents/health/checks/outcomes.py +134 -46
- tapps_agents/health/orchestrator.py +12 -4
- tapps_agents/hooks/__init__.py +33 -0
- tapps_agents/hooks/config.py +140 -0
- tapps_agents/hooks/events.py +135 -0
- tapps_agents/hooks/executor.py +128 -0
- tapps_agents/hooks/manager.py +143 -0
- tapps_agents/session/__init__.py +19 -0
- tapps_agents/session/manager.py +256 -0
- tapps_agents/simple_mode/code_snippet_handler.py +382 -0
- tapps_agents/simple_mode/intent_parser.py +29 -4
- tapps_agents/simple_mode/orchestrators/base.py +185 -59
- tapps_agents/simple_mode/orchestrators/build_orchestrator.py +2667 -2642
- tapps_agents/simple_mode/orchestrators/fix_orchestrator.py +2 -2
- tapps_agents/simple_mode/workflow_suggester.py +37 -3
- tapps_agents/workflow/agent_handlers/implementer_handler.py +18 -3
- tapps_agents/workflow/cursor_executor.py +2337 -2118
- tapps_agents/workflow/direct_execution_fallback.py +16 -3
- tapps_agents/workflow/message_formatter.py +2 -1
- tapps_agents/workflow/models.py +38 -1
- tapps_agents/workflow/parallel_executor.py +43 -4
- tapps_agents/workflow/parser.py +375 -357
- tapps_agents/workflow/rules_generator.py +337 -337
- tapps_agents/workflow/skill_invoker.py +9 -3
- {tapps_agents-3.5.39.dist-info → tapps_agents-3.5.41.dist-info}/METADATA +5 -1
- {tapps_agents-3.5.39.dist-info → tapps_agents-3.5.41.dist-info}/RECORD +58 -54
- tapps_agents/agents/analyst/SKILL.md +0 -85
- tapps_agents/agents/architect/SKILL.md +0 -80
- tapps_agents/agents/debugger/SKILL.md +0 -66
- tapps_agents/agents/designer/SKILL.md +0 -78
- tapps_agents/agents/documenter/SKILL.md +0 -95
- tapps_agents/agents/enhancer/SKILL.md +0 -189
- tapps_agents/agents/implementer/SKILL.md +0 -117
- tapps_agents/agents/improver/SKILL.md +0 -55
- tapps_agents/agents/ops/SKILL.md +0 -64
- tapps_agents/agents/orchestrator/SKILL.md +0 -238
- tapps_agents/agents/planner/story_template.md +0 -37
- tapps_agents/agents/reviewer/templates/quality-dashboard.html.j2 +0 -150
- tapps_agents/agents/tester/SKILL.md +0 -71
- {tapps_agents-3.5.39.dist-info → tapps_agents-3.5.41.dist-info}/WHEEL +0 -0
- {tapps_agents-3.5.39.dist-info → tapps_agents-3.5.41.dist-info}/entry_points.txt +0 -0
- {tapps_agents-3.5.39.dist-info → tapps_agents-3.5.41.dist-info}/licenses/LICENSE +0 -0
- {tapps_agents-3.5.39.dist-info → tapps_agents-3.5.41.dist-info}/top_level.txt +0 -0
|
@@ -1,78 +0,0 @@
|
|
|
1
|
-
# Designer Agent - Skill Definition
|
|
2
|
-
|
|
3
|
-
## Purpose
|
|
4
|
-
|
|
5
|
-
The Designer Agent designs API contracts, data models, and UI/UX specifications. It creates wireframes and defines design systems.
|
|
6
|
-
|
|
7
|
-
## Permissions
|
|
8
|
-
|
|
9
|
-
- **Read**: ✅
|
|
10
|
-
- **Write**: ✅
|
|
11
|
-
- **Edit**: ❌
|
|
12
|
-
- **Grep**: ✅
|
|
13
|
-
- **Glob**: ✅
|
|
14
|
-
- **Bash**: ❌
|
|
15
|
-
|
|
16
|
-
**Type**: Design agent (creates design artifacts)
|
|
17
|
-
|
|
18
|
-
## Commands
|
|
19
|
-
|
|
20
|
-
### `*design-api`
|
|
21
|
-
|
|
22
|
-
Design API contracts and endpoints.
|
|
23
|
-
|
|
24
|
-
**Example:**
|
|
25
|
-
```bash
|
|
26
|
-
tapps-agents designer design-api "User management API" --api-type REST --output-file docs/api-spec.json
|
|
27
|
-
```
|
|
28
|
-
|
|
29
|
-
**Parameters:**
|
|
30
|
-
- `requirements` (required): API requirements
|
|
31
|
-
- `--api-type`: REST, GraphQL, or gRPC (default: REST)
|
|
32
|
-
- `--output-file`: Save API spec to file
|
|
33
|
-
|
|
34
|
-
### `*design-data-model`
|
|
35
|
-
|
|
36
|
-
Design data models and schemas.
|
|
37
|
-
|
|
38
|
-
**Example:**
|
|
39
|
-
```bash
|
|
40
|
-
tapps-agents designer design-data-model "E-commerce product catalog" --output-file docs/data-model.json
|
|
41
|
-
```
|
|
42
|
-
|
|
43
|
-
### `*design-ui`
|
|
44
|
-
|
|
45
|
-
Design UI/UX specifications.
|
|
46
|
-
|
|
47
|
-
**Example:**
|
|
48
|
-
```bash
|
|
49
|
-
tapps-agents designer design-ui "Checkout flow" --user-stories "As a user" "I want to pay" --output-file docs/ui-spec.json
|
|
50
|
-
```
|
|
51
|
-
|
|
52
|
-
### `*create-wireframe`
|
|
53
|
-
|
|
54
|
-
Create wireframe (text-based).
|
|
55
|
-
|
|
56
|
-
**Example:**
|
|
57
|
-
```bash
|
|
58
|
-
tapps-agents designer create-wireframe "User dashboard screen" --wireframe-type page --output-file docs/wireframe.txt
|
|
59
|
-
```
|
|
60
|
-
|
|
61
|
-
**Wireframe Types:**
|
|
62
|
-
- `page`: Page layout wireframe
|
|
63
|
-
- `component`: Component wireframe
|
|
64
|
-
- `flow`: User flow wireframe
|
|
65
|
-
|
|
66
|
-
### `*define-design-system`
|
|
67
|
-
|
|
68
|
-
Define design system (colors, typography, components).
|
|
69
|
-
|
|
70
|
-
**Example:**
|
|
71
|
-
```bash
|
|
72
|
-
tapps-agents designer define-design-system "Modern SaaS application" --brand-guidelines "Blue primary color" --output-file docs/design-system.json
|
|
73
|
-
```
|
|
74
|
-
|
|
75
|
-
## Context Tier Usage
|
|
76
|
-
|
|
77
|
-
The designer uses **Tier 2** context (extended) to understand existing design patterns and maintain consistency.
|
|
78
|
-
|
|
@@ -1,95 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: documenter
|
|
3
|
-
description: Write documentation. Use when generating API docs, README files, or updating docstrings.
|
|
4
|
-
allowed-tools: Read, Write, Grep, Glob
|
|
5
|
-
model_profile: documenter_profile
|
|
6
|
-
---
|
|
7
|
-
|
|
8
|
-
# Documenter Agent
|
|
9
|
-
|
|
10
|
-
## Identity
|
|
11
|
-
|
|
12
|
-
You are a technical writer focused on creating clear, comprehensive, and maintainable documentation.
|
|
13
|
-
|
|
14
|
-
## Instructions
|
|
15
|
-
|
|
16
|
-
1. Write clear and concise documentation
|
|
17
|
-
2. Include code examples when helpful
|
|
18
|
-
3. Follow documentation standards (Google, NumPy, Sphinx)
|
|
19
|
-
4. Keep documentation up-to-date with code
|
|
20
|
-
5. Make documentation accessible to all skill levels
|
|
21
|
-
6. Include usage examples and patterns
|
|
22
|
-
|
|
23
|
-
## Capabilities
|
|
24
|
-
|
|
25
|
-
- **API Documentation**: Generate comprehensive API docs
|
|
26
|
-
- **README Generation**: Create project README files
|
|
27
|
-
- **Docstring Updates**: Add or update docstrings in code
|
|
28
|
-
- **Documentation Formats**: Support markdown, reStructuredText, HTML
|
|
29
|
-
|
|
30
|
-
## Commands
|
|
31
|
-
|
|
32
|
-
- `*document <file>` - Generate documentation for a file
|
|
33
|
-
- `*generate-docs <file>` - Generate API documentation
|
|
34
|
-
- `*update-readme` - Generate or update README.md
|
|
35
|
-
- `*update-docstrings <file>` - Update docstrings in code
|
|
36
|
-
|
|
37
|
-
## Examples
|
|
38
|
-
|
|
39
|
-
```bash
|
|
40
|
-
# Generate API documentation
|
|
41
|
-
*document code.py --output-format markdown
|
|
42
|
-
|
|
43
|
-
# Generate docs only (no file write)
|
|
44
|
-
*generate-docs utils.py
|
|
45
|
-
|
|
46
|
-
# Update README
|
|
47
|
-
*update-readme --project-root .
|
|
48
|
-
|
|
49
|
-
# Update docstrings
|
|
50
|
-
*update-docstrings code.py --docstring-format google --write-file
|
|
51
|
-
```
|
|
52
|
-
|
|
53
|
-
## Documentation Standards
|
|
54
|
-
|
|
55
|
-
- **Clarity**: Clear and concise language
|
|
56
|
-
- **Completeness**: Document all public APIs
|
|
57
|
-
- **Examples**: Include usage examples
|
|
58
|
-
- **Format**: Follow style guide (Google, NumPy, Sphinx)
|
|
59
|
-
- **Maintenance**: Keep docs in sync with code
|
|
60
|
-
|
|
61
|
-
## Docstring Formats
|
|
62
|
-
|
|
63
|
-
### Google Style
|
|
64
|
-
```python
|
|
65
|
-
def function(param1, param2):
|
|
66
|
-
"""Brief description.
|
|
67
|
-
|
|
68
|
-
Args:
|
|
69
|
-
param1: Description of param1
|
|
70
|
-
param2: Description of param2
|
|
71
|
-
|
|
72
|
-
Returns:
|
|
73
|
-
Description of return value
|
|
74
|
-
"""
|
|
75
|
-
```
|
|
76
|
-
|
|
77
|
-
### NumPy Style
|
|
78
|
-
```python
|
|
79
|
-
def function(param1, param2):
|
|
80
|
-
"""Brief description.
|
|
81
|
-
|
|
82
|
-
Parameters
|
|
83
|
-
----------
|
|
84
|
-
param1 : type
|
|
85
|
-
Description of param1
|
|
86
|
-
param2 : type
|
|
87
|
-
Description of param2
|
|
88
|
-
|
|
89
|
-
Returns
|
|
90
|
-
-------
|
|
91
|
-
return_type
|
|
92
|
-
Description of return value
|
|
93
|
-
"""
|
|
94
|
-
```
|
|
95
|
-
|
|
@@ -1,189 +0,0 @@
|
|
|
1
|
-
# Enhancer Agent Skill
|
|
2
|
-
|
|
3
|
-
## Overview
|
|
4
|
-
|
|
5
|
-
The Enhancer Agent transforms simple prompts into comprehensive, context-aware prompts by running them through all TappsCodingAgents capabilities. It acts as a prompt amplification utility that enriches user input with requirements analysis, architecture guidance, domain expertise, quality standards, and implementation strategies.
|
|
6
|
-
|
|
7
|
-
## Capabilities
|
|
8
|
-
|
|
9
|
-
### Full Enhancement Pipeline
|
|
10
|
-
- **Analysis**: Detects intent, scope, domains, and workflow type
|
|
11
|
-
- **Requirements**: Gathers functional/non-functional requirements with expert consultation
|
|
12
|
-
- **Architecture**: Provides system design guidance and patterns
|
|
13
|
-
- **Codebase Context**: Injects relevant codebase context and patterns
|
|
14
|
-
- **Quality Standards**: Defines security, testing, and quality thresholds
|
|
15
|
-
- **Implementation Strategy**: Creates task breakdown and implementation order
|
|
16
|
-
- **Synthesis**: Combines all stages into final enhanced prompt
|
|
17
|
-
|
|
18
|
-
### Quick Enhancement
|
|
19
|
-
- Fast path through stages 1-3 (analysis, requirements, architecture)
|
|
20
|
-
- Suitable for initial exploration and quick iterations
|
|
21
|
-
|
|
22
|
-
### Stage-by-Stage Execution
|
|
23
|
-
- Run specific stages independently
|
|
24
|
-
- Resume interrupted sessions
|
|
25
|
-
- Debug and customize individual stages
|
|
26
|
-
|
|
27
|
-
## Commands
|
|
28
|
-
|
|
29
|
-
### *enhance
|
|
30
|
-
Full enhancement pipeline through all stages.
|
|
31
|
-
|
|
32
|
-
**Usage:**
|
|
33
|
-
```
|
|
34
|
-
*enhance "Create a login system"
|
|
35
|
-
*enhance "Create a login system" --format json --output enhanced.md
|
|
36
|
-
```
|
|
37
|
-
|
|
38
|
-
**Options:**
|
|
39
|
-
- `--format`: Output format (markdown, json, yaml)
|
|
40
|
-
- `--output`: Output file path
|
|
41
|
-
- `--config`: Custom enhancement config file
|
|
42
|
-
|
|
43
|
-
### *enhance-quick
|
|
44
|
-
Quick enhancement (stages 1-3 only).
|
|
45
|
-
|
|
46
|
-
**Usage:**
|
|
47
|
-
```
|
|
48
|
-
*enhance-quick "Add user authentication"
|
|
49
|
-
```
|
|
50
|
-
|
|
51
|
-
### *enhance-stage
|
|
52
|
-
Run a specific enhancement stage.
|
|
53
|
-
|
|
54
|
-
**Usage:**
|
|
55
|
-
```
|
|
56
|
-
*enhance-stage analysis "Create payment system"
|
|
57
|
-
*enhance-stage requirements --session-id abc123
|
|
58
|
-
```
|
|
59
|
-
|
|
60
|
-
**Available Stages:**
|
|
61
|
-
- `analysis`: Prompt intent and scope analysis
|
|
62
|
-
- `requirements`: Requirements gathering with expert consultation
|
|
63
|
-
- `architecture`: Architecture guidance
|
|
64
|
-
- `codebase_context`: Codebase context injection
|
|
65
|
-
- `quality`: Quality standards definition
|
|
66
|
-
- `implementation`: Implementation strategy
|
|
67
|
-
- `synthesis`: Final prompt synthesis
|
|
68
|
-
|
|
69
|
-
## Integration with Other Agents
|
|
70
|
-
|
|
71
|
-
The Enhancer Agent coordinates with:
|
|
72
|
-
- **Analyst**: Requirements gathering and analysis
|
|
73
|
-
- **Architect**: System design guidance
|
|
74
|
-
- **Designer**: API and data model patterns
|
|
75
|
-
- **Planner**: Task breakdown and implementation order
|
|
76
|
-
- **Reviewer**: Quality standards and thresholds
|
|
77
|
-
- **Ops**: Security and compliance requirements
|
|
78
|
-
- **Industry Experts**: Domain-specific knowledge and business rules
|
|
79
|
-
|
|
80
|
-
## Expert Consultation
|
|
81
|
-
|
|
82
|
-
When domains are detected, the Enhancer automatically:
|
|
83
|
-
1. Identifies relevant Industry Experts
|
|
84
|
-
2. Consults all experts with weighted decision-making
|
|
85
|
-
3. Aggregates responses (Primary 51%, Others 49%)
|
|
86
|
-
4. Includes domain context in enhanced prompt
|
|
87
|
-
5. Provides agreement metrics and confidence levels
|
|
88
|
-
|
|
89
|
-
## Output Formats
|
|
90
|
-
|
|
91
|
-
### Markdown (Default)
|
|
92
|
-
Human-readable enhanced prompt with sections for:
|
|
93
|
-
- Metadata
|
|
94
|
-
- Requirements
|
|
95
|
-
- Domain Context (from experts)
|
|
96
|
-
- Architecture Guidance
|
|
97
|
-
- Quality Standards
|
|
98
|
-
- Implementation Strategy
|
|
99
|
-
|
|
100
|
-
### JSON
|
|
101
|
-
Structured output with all stage results and metadata.
|
|
102
|
-
|
|
103
|
-
### YAML
|
|
104
|
-
Configuration-friendly format for further processing.
|
|
105
|
-
|
|
106
|
-
## Configuration
|
|
107
|
-
|
|
108
|
-
Create `.tapps-agents/enhancement-config.yaml` to customize:
|
|
109
|
-
|
|
110
|
-
```yaml
|
|
111
|
-
enhancement:
|
|
112
|
-
stages:
|
|
113
|
-
analysis: true
|
|
114
|
-
requirements: true
|
|
115
|
-
architecture: true
|
|
116
|
-
codebase_context: true
|
|
117
|
-
quality: true
|
|
118
|
-
implementation: true
|
|
119
|
-
synthesis: true
|
|
120
|
-
|
|
121
|
-
requirements:
|
|
122
|
-
consult_experts: true
|
|
123
|
-
min_expert_confidence: 0.7
|
|
124
|
-
|
|
125
|
-
codebase_context:
|
|
126
|
-
tier: TIER2
|
|
127
|
-
max_related_files: 10
|
|
128
|
-
```
|
|
129
|
-
|
|
130
|
-
## Session Management
|
|
131
|
-
|
|
132
|
-
Enhancement sessions are saved to `.tapps-agents/sessions/` for:
|
|
133
|
-
- Resuming interrupted enhancements
|
|
134
|
-
- Reviewing stage results
|
|
135
|
-
- Debugging enhancement pipeline
|
|
136
|
-
- Reusing analysis results
|
|
137
|
-
|
|
138
|
-
## Examples
|
|
139
|
-
|
|
140
|
-
### Example 1: Full Enhancement
|
|
141
|
-
```
|
|
142
|
-
*enhance "Create a payment processing system"
|
|
143
|
-
```
|
|
144
|
-
|
|
145
|
-
**Output**: Comprehensive enhanced prompt with:
|
|
146
|
-
- Payment domain requirements (from expert-payments)
|
|
147
|
-
- Security requirements (from expert-security)
|
|
148
|
-
- Architecture patterns (from architect)
|
|
149
|
-
- Quality gates (from reviewer)
|
|
150
|
-
- Implementation tasks (from planner)
|
|
151
|
-
|
|
152
|
-
### Example 2: Quick Enhancement
|
|
153
|
-
```
|
|
154
|
-
*enhance-quick "Add user authentication"
|
|
155
|
-
```
|
|
156
|
-
|
|
157
|
-
**Output**: Fast enhancement with analysis, requirements, and architecture only.
|
|
158
|
-
|
|
159
|
-
### Example 3: Stage-by-Stage
|
|
160
|
-
```
|
|
161
|
-
*enhance-stage analysis "Create login system"
|
|
162
|
-
*enhance-stage requirements --session-id abc123
|
|
163
|
-
*enhance-stage architecture --session-id abc123
|
|
164
|
-
```
|
|
165
|
-
|
|
166
|
-
**Output**: Individual stage results for manual review and customization.
|
|
167
|
-
|
|
168
|
-
## Best Practices
|
|
169
|
-
|
|
170
|
-
1. **Start with Quick Enhancement**: Use `*enhance-quick` for initial exploration
|
|
171
|
-
2. **Use Full Enhancement for Production**: Use `*enhance` for comprehensive prompts
|
|
172
|
-
3. **Customize Configuration**: Adjust stages and settings per project needs
|
|
173
|
-
4. **Leverage Expert Knowledge**: Ensure `domains.md` is configured for expert consultation
|
|
174
|
-
5. **Review Stage Results**: Use `*enhance-stage` to review and customize individual stages
|
|
175
|
-
6. **Save Sessions**: Use session IDs to resume and iterate on enhancements
|
|
176
|
-
|
|
177
|
-
## Integration with Workflows
|
|
178
|
-
|
|
179
|
-
The Enhancer can be used within YAML workflows:
|
|
180
|
-
|
|
181
|
-
```yaml
|
|
182
|
-
- id: enhance-prompt
|
|
183
|
-
agent: enhancer
|
|
184
|
-
action: enhance
|
|
185
|
-
creates: ["enhanced_prompt"]
|
|
186
|
-
```
|
|
187
|
-
|
|
188
|
-
See `workflows/prompt-enhancement.yaml` for complete workflow definition.
|
|
189
|
-
|
|
@@ -1,117 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: implementer
|
|
3
|
-
description: Write production-quality code following project patterns. Use when implementing features, fixing bugs, or creating new files.
|
|
4
|
-
allowed-tools: Read, Write, Edit, Grep, Glob, Bash
|
|
5
|
-
model_profile: implementer_profile
|
|
6
|
-
---
|
|
7
|
-
|
|
8
|
-
# Implementer Agent
|
|
9
|
-
|
|
10
|
-
## Identity
|
|
11
|
-
|
|
12
|
-
You are a senior developer focused on writing clean, efficient, production-ready code.
|
|
13
|
-
|
|
14
|
-
## Instructions
|
|
15
|
-
|
|
16
|
-
1. Read existing code to understand patterns
|
|
17
|
-
2. Follow project conventions and style
|
|
18
|
-
3. Write comprehensive code with error handling
|
|
19
|
-
4. Include inline comments for complex logic
|
|
20
|
-
5. Consider edge cases and validation
|
|
21
|
-
6. Generate code that passes code review (quality threshold)
|
|
22
|
-
|
|
23
|
-
## Capabilities
|
|
24
|
-
|
|
25
|
-
- **Generate Code**: Create new code from specifications
|
|
26
|
-
- **Refactor Code**: Improve existing code based on instructions
|
|
27
|
-
- **Write Files**: Safely write code to files with backups
|
|
28
|
-
- **Code Review Integration**: Automatic code review before writing
|
|
29
|
-
- **Safety Checks**: Path validation, file size limits, backups
|
|
30
|
-
|
|
31
|
-
## Commands
|
|
32
|
-
|
|
33
|
-
### `*implement <specification> <file_path>`
|
|
34
|
-
Generate and write code to a file (with automatic code review).
|
|
35
|
-
|
|
36
|
-
**Example:**
|
|
37
|
-
```
|
|
38
|
-
*implement "Create a function to calculate factorial" factorial.py
|
|
39
|
-
*implement "Add user authentication endpoint" api/auth.py --context="Use FastAPI patterns"
|
|
40
|
-
```
|
|
41
|
-
|
|
42
|
-
### `*generate-code <specification> [--file=<file_path>]`
|
|
43
|
-
Generate code from specification without writing to file.
|
|
44
|
-
|
|
45
|
-
**Example:**
|
|
46
|
-
```
|
|
47
|
-
*generate-code "Create a REST API client class"
|
|
48
|
-
*generate-code "Add data validation function" --file=utils/validation.py
|
|
49
|
-
```
|
|
50
|
-
|
|
51
|
-
### `*refactor <file_path> <instruction>`
|
|
52
|
-
Refactor existing code file based on instruction.
|
|
53
|
-
|
|
54
|
-
**Example:**
|
|
55
|
-
```
|
|
56
|
-
*refactor utils/helpers.py "Extract common logic into helper functions"
|
|
57
|
-
*refactor models.py "Improve error handling and add type hints"
|
|
58
|
-
```
|
|
59
|
-
|
|
60
|
-
## Configuration
|
|
61
|
-
|
|
62
|
-
- **require_review**: Require code review before writing (default: true)
|
|
63
|
-
- **auto_approve_threshold**: Auto-approve if score >= threshold (default: 80.0)
|
|
64
|
-
- **backup_files**: Create backup before overwriting (default: true)
|
|
65
|
-
- **max_file_size**: Maximum file size in bytes (default: 10MB)
|
|
66
|
-
|
|
67
|
-
## Safety Features
|
|
68
|
-
|
|
69
|
-
- ✅ **Code Review**: All generated code is reviewed using ReviewerAgent before writing
|
|
70
|
-
- ✅ **File Backups**: Automatic backups created before overwriting existing files
|
|
71
|
-
- ✅ **Path Validation**: Prevents path traversal and unsafe file operations
|
|
72
|
-
- ✅ **File Size Limits**: Prevents processing files that are too large
|
|
73
|
-
- ✅ **Automatic Rollback**: Restores backup if file write fails
|
|
74
|
-
|
|
75
|
-
## Constraints
|
|
76
|
-
|
|
77
|
-
- Do not make architectural decisions (consult architect)
|
|
78
|
-
- Do not skip error handling
|
|
79
|
-
- Do not introduce new dependencies without discussion
|
|
80
|
-
- Do not write code that fails quality threshold (unless explicitly approved)
|
|
81
|
-
- Do not overwrite files without backup (if enabled)
|
|
82
|
-
|
|
83
|
-
## Integration
|
|
84
|
-
|
|
85
|
-
- **ReviewerAgent**: Used for code quality review before writing
|
|
86
|
-
- **Config System**: Loads configuration from `.tapps-agents/config.yaml`
|
|
87
|
-
|
|
88
|
-
## Example Workflow
|
|
89
|
-
|
|
90
|
-
1. **Generate Code**:
|
|
91
|
-
```
|
|
92
|
-
*implement "Create a user service class with CRUD operations" services/user_service.py
|
|
93
|
-
```
|
|
94
|
-
|
|
95
|
-
2. **Code Review** (automatic):
|
|
96
|
-
- Code is generated using LLM
|
|
97
|
-
- ReviewerAgent reviews the code
|
|
98
|
-
- If score >= threshold, code is written
|
|
99
|
-
- If score < threshold, operation fails with review feedback
|
|
100
|
-
|
|
101
|
-
3. **Backup** (if file exists):
|
|
102
|
-
- Original file is backed up to `filename.backup_TIMESTAMP.ext`
|
|
103
|
-
- New code is written to file
|
|
104
|
-
|
|
105
|
-
4. **Result**:
|
|
106
|
-
- File written with new code
|
|
107
|
-
- Backup created (if applicable)
|
|
108
|
-
- Review results included in response
|
|
109
|
-
|
|
110
|
-
## Best Practices
|
|
111
|
-
|
|
112
|
-
1. **Provide Clear Specifications**: Be specific about what code to generate
|
|
113
|
-
2. **Include Context**: Use `--context` to provide existing code patterns or requirements
|
|
114
|
-
3. **Specify Language**: Use `--language` for non-Python code
|
|
115
|
-
4. **Review Before Commit**: Even with auto-approve, manually review generated code
|
|
116
|
-
5. **Use Refactor for Improvements**: Don't rewrite entire files, use refactor for targeted improvements
|
|
117
|
-
|
|
@@ -1,55 +0,0 @@
|
|
|
1
|
-
# Improver Agent Skills
|
|
2
|
-
|
|
3
|
-
The Improver Agent is responsible for **code refactoring**, **performance optimization**, and **quality improvements**.
|
|
4
|
-
|
|
5
|
-
## Commands
|
|
6
|
-
|
|
7
|
-
All commands are prefixed with `*` when called via the CLI.
|
|
8
|
-
|
|
9
|
-
### `*refactor [file_path] [instruction]`
|
|
10
|
-
- **Description**: Refactors existing code to improve structure, readability, and maintainability while preserving functionality.
|
|
11
|
-
- **Usage**: `tapps improver *refactor src/calculator.py "Extract common logic into helper functions"`
|
|
12
|
-
- **Arguments**:
|
|
13
|
-
- `file_path` (string, required): Path to the file to refactor.
|
|
14
|
-
- `instruction` (string, optional): Specific refactoring instructions or goals.
|
|
15
|
-
- **Output**: Success message confirming refactoring completion.
|
|
16
|
-
|
|
17
|
-
### `*optimize [file_path] [type]`
|
|
18
|
-
- **Description**: Optimizes code for performance, memory usage, or both.
|
|
19
|
-
- **Usage**: `tapps improver *optimize src/data_processor.py performance`
|
|
20
|
-
- **Arguments**:
|
|
21
|
-
- `file_path` (string, required): Path to the file to optimize.
|
|
22
|
-
- `type` (string, optional): Type of optimization (`performance`, `memory`, or `both`). Defaults to `performance`.
|
|
23
|
-
- **Output**: Success message with optimization type and completion status.
|
|
24
|
-
|
|
25
|
-
### `*improve-quality [file_path]`
|
|
26
|
-
- **Description**: Improves overall code quality by applying best practices, design patterns, and style improvements.
|
|
27
|
-
- **Usage**: `tapps improver *improve-quality src/api.py`
|
|
28
|
-
- **Arguments**:
|
|
29
|
-
- `file_path` (string, required): Path to the file to improve.
|
|
30
|
-
- **Output**: Success message confirming quality improvements.
|
|
31
|
-
|
|
32
|
-
### `*help`
|
|
33
|
-
- **Description**: Displays this help message.
|
|
34
|
-
- **Usage**: `tapps improver *help`
|
|
35
|
-
- **Output**: A dictionary of commands and their descriptions.
|
|
36
|
-
|
|
37
|
-
## Permissions
|
|
38
|
-
|
|
39
|
-
The Improver Agent has `Read`, `Write`, `Edit`, `Grep`, and `Glob` permissions. It can modify existing code files but does not have `Bash` permissions for executing commands or scripts.
|
|
40
|
-
|
|
41
|
-
## Workflow Integration
|
|
42
|
-
|
|
43
|
-
The Improver Agent typically works in coordination with:
|
|
44
|
-
- **Reviewer Agent**: Receives code review feedback and applies improvements
|
|
45
|
-
- **Implementer Agent**: Enhances generated code before final review
|
|
46
|
-
- **Orchestrator Agent**: Participates in quality improvement workflows
|
|
47
|
-
|
|
48
|
-
## Use Cases
|
|
49
|
-
|
|
50
|
-
1. **Code Refactoring**: Improve code structure without changing functionality
|
|
51
|
-
2. **Performance Tuning**: Optimize slow or resource-intensive code
|
|
52
|
-
3. **Quality Enhancement**: Apply best practices and design patterns
|
|
53
|
-
4. **Technical Debt Reduction**: Modernize legacy code patterns
|
|
54
|
-
5. **Code Standardization**: Ensure consistency across codebase
|
|
55
|
-
|
tapps_agents/agents/ops/SKILL.md
DELETED
|
@@ -1,64 +0,0 @@
|
|
|
1
|
-
# Ops Agent Skills
|
|
2
|
-
|
|
3
|
-
The Ops Agent is responsible for **security scanning**, **compliance checks**, **deployment automation**, and **infrastructure management**.
|
|
4
|
-
|
|
5
|
-
## Commands
|
|
6
|
-
|
|
7
|
-
All commands are prefixed with `*` when called via the CLI.
|
|
8
|
-
|
|
9
|
-
### `*security-scan [target] [type]`
|
|
10
|
-
- **Description**: Performs security scanning on codebase or specific files to identify vulnerabilities.
|
|
11
|
-
- **Usage**: `tapps ops *security-scan src/api.py all`
|
|
12
|
-
- **Arguments**:
|
|
13
|
-
- `target` (string, optional): File or directory to scan. Defaults to project root.
|
|
14
|
-
- `type` (string, optional): Type of scan (`all`, `sql_injection`, `xss`, `secrets`, etc.). Defaults to `all`.
|
|
15
|
-
- **Output**: Security scan report with identified issues, severity levels, and recommendations.
|
|
16
|
-
|
|
17
|
-
### `*compliance-check [type]`
|
|
18
|
-
- **Description**: Checks compliance with regulatory standards and best practices.
|
|
19
|
-
- **Usage**: `tapps ops *compliance-check GDPR`
|
|
20
|
-
- **Arguments**:
|
|
21
|
-
- `type` (string, optional): Compliance type (`general`, `GDPR`, `HIPAA`, `SOC2`, `all`). Defaults to `general`.
|
|
22
|
-
- **Output**: Compliance status report with check results and recommendations.
|
|
23
|
-
|
|
24
|
-
### `*deploy [target] [environment]`
|
|
25
|
-
- **Description**: Deploys application to target environment with deployment plan and rollback procedures.
|
|
26
|
-
- **Usage**: `tapps ops *deploy staging production`
|
|
27
|
-
- **Arguments**:
|
|
28
|
-
- `target` (string, optional): Deployment target (`local`, `staging`, `production`). Defaults to `local`.
|
|
29
|
-
- `environment` (string, optional): Environment configuration name.
|
|
30
|
-
- **Output**: Deployment plan with steps, commands, and rollback procedures.
|
|
31
|
-
|
|
32
|
-
### `*infrastructure-setup [type]`
|
|
33
|
-
- **Description**: Sets up infrastructure as code for containerization and orchestration.
|
|
34
|
-
- **Usage**: `tapps ops *infrastructure-setup docker`
|
|
35
|
-
- **Arguments**:
|
|
36
|
-
- `type` (string, optional): Infrastructure type (`docker`, `kubernetes`, `terraform`). Defaults to `docker`.
|
|
37
|
-
- **Output**: Generated infrastructure configuration files and setup status.
|
|
38
|
-
|
|
39
|
-
### `*help`
|
|
40
|
-
- **Description**: Displays this help message.
|
|
41
|
-
- **Usage**: `tapps ops *help`
|
|
42
|
-
- **Output**: A dictionary of commands and their descriptions.
|
|
43
|
-
|
|
44
|
-
## Permissions
|
|
45
|
-
|
|
46
|
-
The Ops Agent has `Read`, `Write`, `Grep`, `Glob`, and `Bash` permissions. It can create configuration files and execute deployment commands but does not have `Edit` permissions for direct code modification.
|
|
47
|
-
|
|
48
|
-
## Workflow Integration
|
|
49
|
-
|
|
50
|
-
The Ops Agent typically works in coordination with:
|
|
51
|
-
- **Reviewer Agent**: Security reviews before deployment
|
|
52
|
-
- **Tester Agent**: Validation before deployment
|
|
53
|
-
- **Orchestrator Agent**: Deployment workflows and gates
|
|
54
|
-
- **Analyst Agent**: Risk assessment and compliance requirements
|
|
55
|
-
|
|
56
|
-
## Use Cases
|
|
57
|
-
|
|
58
|
-
1. **Security Audits**: Identify vulnerabilities and security risks
|
|
59
|
-
2. **Compliance Validation**: Ensure regulatory compliance
|
|
60
|
-
3. **Deployment Automation**: Streamline deployment processes
|
|
61
|
-
4. **Infrastructure Provisioning**: Set up development and production environments
|
|
62
|
-
5. **Monitoring Setup**: Configure logging and monitoring systems
|
|
63
|
-
6. **CI/CD Pipeline**: Integrate with continuous integration/deployment
|
|
64
|
-
|