# Tosca Remediating From Results

> Applies fixes to Tosca Cloud test artifacts based on execution failure analysis — test case edits, playlist item renames, and Builder updates. Use when the user asks to fix, update, or remediate failing tests after diagnosis. Requires explicit user approval for destructive changes. Does NOT cover read-only analysis (use tosca-analyzing-execution-results).

- Skill: `tricentis/tosca-remediating-from-results-2` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add tricentis/tosca-remediating-from-results-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tricentis/tosca-remediating-from-results-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- License: Apache-2.0
- Author: Tricentis (https://skillmd.com/u/tricentis)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/tricentis/tosca-remediating-from-results-2

---


# Remediate Tosca Cloud tests from results

Apply ranked fixes from analysis. **Mutating** — confirm scope before edits.

Prerequisite: diagnosis from `tosca-analyzing-execution-results` or user-provided failure detail.

## Session checklist

```text
Remediate Cloud tests:
- [ ] Confirm scope and get user approval
- [ ] Resolve artifacts (inventory search → entityIds)
- [ ] Apply fix per remediation recipe
- [ ] Re-run playlist or re-search artifact
- [ ] Report changes, run ID, outcome, confidence
```

## Fast path

1. **Confirm scope** — which test cases / playlist items to fix; get user approval.
2. **Resolve artifacts** — `tosca_inventory_search` → entityIds.
3. **Apply fix** — per recipe in [references/remediation-recipes.md](references/remediation-recipes.md). Common: playlist item rename (`analyzeTestCaseItems` → `applyTestCaseItemRenames`), API message update, scaffold replacement TC, re-run.
4. **Verify** — re-run playlist (`tosca_playlist_run`) or re-search artifact.
5. **Report** — what changed, new run ID, outcome.

## Persistence

Cloud mutations persist via API immediately. No save/check-in step.

## Destructive operations

Confirm before: `tosca_builder_deleteApiMessage`, `tosca_playlist_deleteById`, folder deletes.

See [references/editability-and-persistence.md](references/editability-and-persistence.md).