levante 0.3.0 → 0.3.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -11
- package/agents/0.init-agent.md +1 -1
- package/dist/cli.js +16875 -80
- package/dist/mcp.js +24 -24
- package/package.json +3 -2
- package/templates/workflow.md +3 -3
package/README.md
CHANGED
|
@@ -173,17 +173,17 @@ Add to your MCP client config (e.g., `claude_desktop_config.json`):
|
|
|
173
173
|
|
|
174
174
|
| Tool | Description |
|
|
175
175
|
|------|-------------|
|
|
176
|
-
| `
|
|
177
|
-
| `
|
|
178
|
-
| `
|
|
179
|
-
| `
|
|
180
|
-
| `
|
|
181
|
-
| `
|
|
182
|
-
| `
|
|
183
|
-
| `
|
|
184
|
-
| `
|
|
185
|
-
| `
|
|
186
|
-
| `
|
|
176
|
+
| `levante_plan_workflow` | Get ordered step list with prerequisite checks |
|
|
177
|
+
| `levante_execute_step` | Execute a single pipeline step |
|
|
178
|
+
| `levante_get_workflow_guide` | Get the full workflow guide |
|
|
179
|
+
| `levante_scan_codebase` | Scan project for test infrastructure |
|
|
180
|
+
| `levante_validate_context` | Validate context.md completeness |
|
|
181
|
+
| `levante_read_agent` | Load an agent prompt by name |
|
|
182
|
+
| `levante_get_example` | Get example context.md template |
|
|
183
|
+
| `levante_scan_ast` | Run AST scanner |
|
|
184
|
+
| `levante_scan_ast_detail` | Drill into routes/components/hooks |
|
|
185
|
+
| `levante_build_qa_map` | Build and validate QA map |
|
|
186
|
+
| `levante_read_qa_map` | Load existing QA map |
|
|
187
187
|
|
|
188
188
|
## Configuration
|
|
189
189
|
|
package/agents/0.init-agent.md
CHANGED
|
@@ -10,7 +10,7 @@ You are a codebase analysis assistant for the levante test automation tool. Your
|
|
|
10
10
|
|
|
11
11
|
This agent is designed to be used directly in your AI tool (Claude Code, Cursor, Gemini CLI, etc.). Start a conversation and ask it to generate your project context.
|
|
12
12
|
|
|
13
|
-
**If the levante MCP server is configured**, call `
|
|
13
|
+
**If the levante MCP server is configured**, call `levante_scan_codebase` to get scan results, then follow this agent's instructions to produce the context file.
|
|
14
14
|
|
|
15
15
|
**If no MCP server**, manually explore the codebase: look at test files, fixtures, playwright config, tsconfig paths, and helper modules.
|
|
16
16
|
|