Automated summary
This skill runs the validation suite for the adviser_allocation engine: pytest tests with coverage, ruff linting, and mypy type checking.
Strengths
- Collects all three validation commands (tests, lint, type check) in one place with the repo's exact syntax.
- Maps each critical area to its test file: allocation algorithm, API endpoints, Firestore operations, and Employment Hero sync.
- Documents the Cloud Run deployment context and the automatic CI/CD deploy on pushes to main.
Limitations
- Commands assume a fixed layout (src/adviser_allocation, tests/) that cannot be configured.
- Does not address dependency installation or the environment variables the tests need.
- Covers neither end-to-end integration testing nor verification of the deployment itself.
Run it right after changing allocation logic, API endpoints, or Firestore interactions, before pushing to main.
Not useful for changes outside the adviser_allocation engine, or when the Python environment and dependencies are not set up.
Security analysis
SafeThe skill only documents standard development commands (pytest, ruff, mypy) and mentions test areas and deployment behavior. No destructive, exfiltrating, or obfuscated actions are instructed.
No concerns found
How this analysis is madeExamples
I just reworked the weighting in the adviser allocation algorithm. Run the full validation suite for adviser_allocation and tell me which tests fail.Before I push to main, run pytest with coverage, ruff and mypy on this repo and summarize any errors I need to fix.I edited the Firestore write path and the Employment Hero sync job — run the relevant tests in tests/test_firestore.py and tests/test_eh_sync.py plus the lint and type checks.Build Validator - adviser_allocation
Validates code changes for the adviser allocation engine.
When to Use
Run after modifying allocation logic, API endpoints, or Firestore interactions.
Commands
# Run tests with coverage
pytest tests/ -v --cov=src/adviser_allocation
# Lint check
uv run ruff check src/ tests/
# Type check
mypy src/
Key Test Areas
- Allocation algorithm:
tests/test_allocation.py - API endpoints:
tests/test_api.py - Firestore operations:
tests/test_firestore.py - Employment Hero sync:
tests/test_eh_sync.py
Deployment Note
This repo deploys to Cloud Run. CI/CD auto-deploys on push to main if tests pass.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/build-validator-adviser-allocation-mtqry3ww/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/build-validator-adviser-allocation-mtqry3ww' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/build-validator-adviser-allocation-mtqry3ww/download' --output '.skill-downloads/build-validator-adviser-allocation-mtqry3ww/SKILL.md.part' && mv '.skill-downloads/build-validator-adviser-allocation-mtqry3ww/SKILL.md.part' '.skill-downloads/build-validator-adviser-allocation-mtqry3ww/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/build-validator-adviser-allocation-mtqry3ww/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.