Menu
Render regression run results from artifacts into deterministic summaries and tables.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create or update deterministic regression plans (`metadata.json`, `contract.json`, `plan.md`) under `.mcpjvm/.../plans/regression`, including ordered trigger steps, optional Watchers for downstream completion checks, and optional external verification for downstream data validity.
Run MCP-first HTTP regression suites (endpoint, service, or API scope) with optional strict probe-hit verification, bounded Watchers for downstream completion checks, and external verification for downstream data validity across HTTP or SQL targets.
Run strict single-line JVM probe verification. Use for line-hit checks, route validation, and fail-closed probe execution.
Manage `.mcpjvm/<project>/projects.json` project context artifacts (read/validate/upsert/list) for runtime contexts, external systems, and health checks.
Create or update deterministic performance plans (`metadata.json`, `contract.json`, `plan.md`) under `.mcpjvm/.../plans/performance`. Use when authoring workload-centric Java performance-suite Artifacts with required strict line-hit verification.
Render performance run results from Artifacts under `.mcpjvm/.../plans/performance/.../runs` into deterministic summaries and threshold tables. Use when summarizing completed Java performance-suite runs.
| name | mcp-java-dev-tools-regression-result |
| description | Render regression run results from artifacts into deterministic summaries and tables. |
Use this workflow to generate run summaries from persisted artifacts under .mcpjvm/<project_name>/plans/regression/<plan>/runs/<run_id>/.
This skill runs in two phases:
ReadRenderDo not render from transient logs when artifacts are available.
Always align with:
references/spec-rules.mdreferences/authoring-checklist.mdreferences/templates/index.mdreferences/templates/http_result_table/endpoint_table_result.mdThese references are bundled with the skill so it remains installable and usable across repositories. If user request conflicts with these rules, fail closed and return deterministic blocked guidance.
Operational source for artifact reads:
artifact_management MCP Tool:
artifactType=run_result, action=read|listArtifact semantics/reference paths:
.mcpjvm/<project_name>/plans/regression/<plan>/runs/<run_id>/execution.result.json.mcpjvm/<project_name>/plans/regression/<plan>/runs/<run_id>/evidence.json.mcpjvm/<project_name>/plans/regression/<plan>/runs/<run_id>/correlation.json for distributed correlation verdict/timeline summary.mcpjvm/<project_name>/plans/regression/<plan>/runs/<run_id>/context.resolved.json for non-secret context displayrun-state.sqlite may supply bounded operational projections, including Watcher checkpoints and attempt progress, but canonical run Artifacts remain the rendering evidence. Do not merge a legacy correlation-index.json into a fresh result. Preserve the distinction between trigger success, Watcher success, and checkpoint/projection failure; a terminal Watcher result is immutable through ordinary runtime writes.
endpoint_table_resultendpoint_table_resultreferences/templates/index.mdSupport user-driven display formats while preserving deterministic field mapping:
table (default)compact (one-line per endpoint)narrative (short summary + top-level metrics)debug (includes deterministic diagnostics and reason codes)For rendered endpoint results, use only these deterministic values:
verified_line_hit: strict Class#method:line probe verification confirmedhttp_only_unverified_line: HTTP-level assertion passed without strict line verificationunknown: coverage could not be deterministically mapped from artifactsn/a: placeholder only for blocked/no-step rows[REDACTED]) as-is.Return deterministic blocked guidance when:
Blocked response must include: