Commands

---
description: 'Safely apply a small change to the testing skill'
---

## UX Prerequisites

1. Read `{{TESTING_SKILL_DIR}}/references/skill-ux-and-behaviour.md` and follow its communication guidelines throughout this command

## What This Does

Controlled maintenance command for applying small, targeted changes to the testing skill. Prevents mistakes by enforcing size limits, correct file targeting, and user approval.

## Arguments

- `$ARGUMENTS` (required): Description of the proposed change

## Phase 1: Validate Input

If `$ARGUMENTS` is empty, stop and print:

> **ERROR**: Describe what you want to change. Usage: `/testskill.update-skill <proposed change>`

## Phase 2: Validate Change Size

Evaluate the proposed change. It must result in **1-3 lines** of added/modified text in a single file.

If the change would require more than 3 lines or touch multiple files, **stop and print:**

> **Too large.** Skill changes must be 1-3 lines in one file. Big text changes risk unintended side effects across the workflow. Please break this into a smaller, more focused change.

## Phase 3: Identify Target File

Read `{{TESTING_SKILL_DIR}}/SKILL.md` to review the full skill structure. Then classify the change into exactly one target file:

| Change is about...                                                                    | Target file                                         |
| ------------------------------------------------------------------------------------- | --------------------------------------------------- |
| How to write test code (patterns, assertions, mocking, DOM, data, anatomy, structure) | The matching file in `references/rules/`            |
| Which workflow steps exist, their sequence, gates, or what gets invoked               | `references/test-workflow.md`                       |
| Test strategy decisions, framework choices, what types of tests to write              | `references/testing-strategy-and-tooling.md`        |
| A specific agent or tool behavior (test-fixer, planner, verifier, page-analyzer)      | `references/tools-and-agents.md`                    |
| Planning logic (how many tests, what the planner decides, plan structure)             | `.cursor/agents/testskill.planner.md`               |
| CLI commands for running/starting tests                                               | `references/test-commands.md`                       |
| Config keys or default values                                                         | `{{CONTEXT_ROOT}}/testskill.config.toml`            |
| A specific command's behavior                                                         | The matching `.cursor/commands/testskill.*.md` file |

**Critical rule**: Never mix topics. If the change spans two areas, stop and ask the user to split it.

Print: `Target file: <path>` and a one-sentence explanation of why.

## Phase 4: Propose and Apply

1. Read the target file
2. Draft the exact edit (1-3 lines), keeping wording concise and consistent with surrounding text
3. Present to the user: the target file, the exact text change (as a diff), and why it belongs there
4. **Wait for user approval.** If the user suggests refinements, iterate until agreed
5. Once approved, apply the edit
6. Increment the minor version in `{{TESTING_SKILL_DIR}}/SKILL.md` (e.g. `3.2` -> `3.3`)

Print: `Done. Skill version bumped to <new version>.`