Skip to content
Skills Library
Programming · Testing

summit

/summit

Runs all tests, updates the journey map, regenerates diagrams with before/after comparison, and reports coverage score. Use when finalizing a coverage sprint, verifying test results, or preparing coverage reports for a PR.

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

Runs all tests, updates the journey map, regenerates diagrams with before/after comparison, and reports coverage score. Use when finalizing a coverage sprint, verifying test results, or preparing coverage reports for a PR.

Original author description

Runs all tests, updates the journey map, regenerates diagrams with before/after comparison, and reports coverage score. Use when finalizing a coverage sprint, verifying test results, or preparing coverage reports for a PR.

How it works

  1. Process
  2. Coverage Thresholds
  3. After Completion
  4. Error Handling
Original SKILL.md headings · 78 lines, 387 words
SKILL.md preview
---
name: summit
description: "Runs all tests, updates the journey map, regenerates diagrams with before/after comparison, and reports coverage score. Use when finalizing a coverage sprint, verifying test results, or preparing coverage reports for a PR."
allowed-tools: Bash, Read, Write, Edit, Glob, Grep
license: MIT
metadata:
  author: Sergio Padron
  version: 3.0.0
---

# Summiting

Run all tests, update the journey map, regenerate diagrams with before/after comparison, and report coverage.

## Process

Copy this checklist and track progress:

```
Summit Progress:
- [ ] Step 1: Save baseline (if starting fresh)
- [ ] Step 2: Run full UI test suite
- [ ] Step 3: Update journeys.json with results
- [ ] Step 4: Regenerate diagrams
- [ ] Step 5: Compute coverage score
- [ ] Step 6: Commit results
- [ ] Step 7: Include diagrams in PR (if applicable)
```

1. **Save baseline (if starting fresh):** If no baseline exists yet, one is auto-created on diagram generation. To explicitly reset the baseline before a test run:
```bash
python3 "${CLAUDE_SKILL_DIR}/../pathfinder/scripts/generate-diagrams.py" <testDir>/pathfinder/journeys.json --save-baseline
```

2. **Run the full UI test suite** using the detected framework. Read the matching framework reference for commands.
```bash
python3 "${CLAUDE_SKILL_DIR}/../pathfinder/scripts/detect-ui-framework.py" .
# Then run the appropriate command (e.g., tuist test, xcodebuild test, npx playwright test)
```

3. **For each test result**, update `<testDir>/pathfinder/journeys.json`:
   - Test passes → `"tested": true`
   - Test fails → `"tested": false` (regression or incomplete implementation)
   - Test disabled with comment → `"tested": "partial"` with `"note"` explaining why

4. **Regenerate diagrams:**
```bash
python3 "${CLAUDE_SKILL_DIR}/../pathfinder/scripts/generate-diagrams.py" <testDir>/pathfinder/journeys.json
```

5. **Compute coverage score:**
```bash
python3 "${CLAUDE_SKILL_DIR}/../pathfinder/scripts/coverage-score.py" <testDir>/pathfinder/journeys.json
```

6. **Commit:**
```bash
git add <testDir>/pathfinder/
git commit -m "Verify: Coverage at X% (Y/Z steps tested)"
```

7. **If creating a PR**, include the diagrams and coverage delta from `<testDir>/pathfinder/blazes.md` in the PR body. The before/after comparison shows reviewers exactly what improved.

## Coverage Thresholds

| Coverage | Status | Action |
|----------|--------|--------|
| 🟢 80%+ | Excellent | Merge-ready |
| 🟡 50-79% | Acceptable | Document gaps, mark partial steps with notes |
| 🔴 <50% | Insufficient | Continue scouting |

## After Completion

When a coverage sprint is done, reset the baseline for the next round:
```bash
python3 "${CLAUDE_SKILL_DIR}/../pathfinder/scripts/generate-diagrams.py" <testDir>/pathfinder/journeys.json --save-baseline
```

This makes the current coverage the new "before" for future comparison.

## Error Handling

- Tests fail that previously passed → regression. Fix before proceeding.
- Coverage drops after code changes → new untested journeys. Re-run `/map`.
- Framework not available (no simulator/emulator) → mark steps as `tested: "partial"`, note the limitation.
- Disabled tests → keep them in the codebase with clear comments; mark as `"partial"` in journeys.json.

Versions

RepositoryScoreLicence
This page · srpadrono/pathfinder100MIT
vickydotbat/vicky-skills90MIT

Database snapshot: 13.11.2026 · package version 6bfd5b533504 (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

  • 100map
    Crawls a codebase to discover all user journeys and creates a journey map (journeys.json) with test coverage status. Use when starting UI test coverage work, auditing existing coverage, or exploring a new codebase's user flows.
  • 100test-full
    Every tier in pyramid order — unit, then integration, then E2E. Use when running all tests before a PR or commit, or generating a coverage report.
  • 100blaze
    Generates Mermaid flowcharts and decision trees from journeys.json showing test coverage with before/after comparison. Use when visualizing coverage, generating diagrams, or showing progress since last sprint.
  • 100improving-python-coverage
    Runs Python unit tests with coverage, analyzes coverage reports, and implements meaningful tests to increase coverage by ~0.2%. Use when you want to systematically improve Python test coverage with high-value test cases.
  • 100improving-frontend-coverage
    Runs frontend unit tests with coverage, analyzes coverage reports, and implements meaningful tests to increase coverage by ~0.2%. Use when you want to systematically improve frontend test coverage with high-value test cases.
  • 100test-updates
    Updates, generates, and validates tests using git-workspace context and TDD/BDD methodology. Use when code changes require new or updated test coverage.

Feedback and reports

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