Skip to content
Skills Library
Programming · Testing

scout

/scout

Writes UI tests for untested steps in the journey map using framework-correct selectors, waits, and patterns. Use when writing tests to fill coverage gaps or generating E2E tests for untested journey steps.

Repository
pathfinder ↗
Licence
MIT
Last repository change
24.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Writes UI tests for untested steps in the journey map using framework-correct selectors, waits, and patterns. Use when writing tests to fill coverage gaps or generating E2E tests for untested journey steps.

Original author description

Writes UI tests for untested steps in the journey map using framework-correct selectors, waits, and patterns. Use when writing tests to fill coverage gaps or generating E2E tests for untested journey steps.

How it works

  1. Process
  2. Error Handling
Original SKILL.md headings · 58 lines, 403 words
SKILL.md preview
---
name: scout
description: "Writes UI tests for untested steps in the journey map using framework-correct selectors, waits, and patterns. Use when writing tests to fill coverage gaps or generating E2E tests for untested journey steps."
allowed-tools: Bash, Read, Write, Edit, Glob, Grep
license: MIT
metadata:
  author: Sergio Padron
  version: 3.0.0
---

# Scouting

Write UI tests for every untested step in the journey map. Each test verifies that a user journey step works correctly.

## Process

1. **Read the journey map:** `<testDir>/pathfinder/journeys.json`
2. **Read the diagram:** `<testDir>/pathfinder/blazes.md` — identify all untested steps. The decision tree makes gaps easy to spot.
3. **Prioritize:** Critical journeys first (auth, core CRUD), then secondary flows, then error paths.

For each untested step:

4. **Read existing test patterns** in the project. Match the style, naming conventions, and test architecture already in use (e.g., BDD protocols, page objects, test fixtures).
5. **Read framework reference:** Load the matching framework reference from the pathfinder skill for correct selectors, waits, and patterns.
6. **Generate test:**
```bash
python3 "${CLAUDE_SKILL_DIR}/../pathfinder/scripts/generate-ui-test.py" <STEP-ID> "<action>" <framework> --route <screen> --auto
```
   - `--auto` appends to existing journey file if found, creates new file if not.
7. **Fill in the test** with real selectors, actions, and assertions matching the actual UI.
   - Use localized strings from the project's resources (e.g., `Localizable.strings`) for button labels.
   - Match the existing test hierarchy/protocol patterns.
8. **Run the test.**
   - **Passes** → the feature works, step is now covered. Mark `tested: true`.
   - **Fails** → either the test needs fixing (wrong selector) or a real bug was found. Investigate before marking.
9. **Update `journeys.json`:** Set `tested: true` and add `testFile` for the step.
10. **Commit per journey:**
```bash
git add <test files> <testDir>/pathfinder/journeys.json
git commit -m "Scout: Test <JOURNEY> journey (N steps)"
```

### Handling untestable steps

Some steps can't pass in the current test environment (e.g., mock API always succeeds, no error injection):
- Write the test anyway so it's ready when the test infrastructure supports it
- Disable the test with a clear comment explaining the blocker
- Mark the step as `"tested": "partial"` with a `"note"` field:
```json
{ "id": "ERROR-01", "tested": "partial", "note": "test disabled — mock API always succeeds, needs failure injection" }
```

After testing a batch:

11. **Regenerate diagrams:**
```bash
python3 "${CLAUDE_SKILL_DIR}/../pathfinder/scripts/generate-diagrams.py" <testDir>/pathfinder/journeys.json
```
    - The before/after comparison will show your progress since the baseline
12. **Commit:** `git add <testDir>/pathfinder/blazes.md && git commit -m "Diagram: Coverage now X%"`

## Error Handling

- Framework not installed → run `python3 "${CLAUDE_SKILL_DIR}/../pathfinder/scripts/detect-ui-framework.py" .` and install.
- Test fails due to wrong selector → read the component source and localized strings, fix the selector.
- Step is untestable (native OS dialog, third-party auth redirect) → mark `tested: "partial"` with a note.

Versions

RepositoryScoreLicence
This page · srpadrono/pathfinder100MIT
anton-abyzov/vskill100MIT
mcorbett51090/ravenclaude100MIT
kovrichard/portable-agent-layer100MIT
vanducng/skills100MIT
ahmad-punch/oss-contributor100MIT
udaysharmadev/Skills100MIT
dodobrands/scout100Apache-2.0
vaayne/agent-kit100MIT

Database snapshot: 13.11.2026 · package version 2971d0e31f8c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100smart-test
    Find test gaps and generate tests for uncovered code. Triggers on: generate tests, write tests, test coverage, find untested code, test gaps, smart test, what needs testing.
  • 100analyzing-test-coverage
    Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".
  • 100analyzing-test-coverage
    Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".
  • 100generate-tests
    Use when asked to generate tests for a file, module or component, to raise coverage, or to bootstrap a suite for untested code. Detects the project's test framework and conventions first, then writes unit, integration and edge-case tests.
  • 90test-gen
    Use when generating tests for untested code — happy path, edge cases, error handling
  • 100test-coverage-improver
    Analyze test coverage gaps and generate tests to improve coverage. Use when improving test coverage, finding untested code, or writing missing tests.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.