Skip to content
Skills Library
Programming · Testing

validate

/validate

Use this workflow skill for broader project validation across lint, build, formatting, config, and platform checks; prefer test when the request is only about executing tests.

Repository
auto-mobile ↗
Licence
Apache-2.0
Last repository change
28.10.2026

Assessment and security

90/ 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.
Content25 / 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 28.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use this workflow skill for broader project validation across lint, build, formatting, config, and platform checks; prefer test when the request is only about executing tests.

Original author description

Use this workflow skill for broader project validation across lint, build, formatting, config, and platform checks; prefer test when the request is only about executing tests.

How it works

  1. Baseline Validation
  2. Repo Script Validation
  3. Selection Rules
Original SKILL.md headings · 37 lines, 224 words
SKILL.md preview
---
name: validate
description: Use this workflow skill for broader project validation across lint, build, formatting, config, and platform checks; prefer test when the request is only about executing tests.
---

# Validate Changes

Run the lightest validation that covers the touched code, then widen only when needed.

- Prefer `validate` for multi-check verification.
- Prefer `test` when the request is specifically about running tests or reproducing a test failure.
- Before inventing a validation command, check `scripts/` and `scripts/README.md` for an existing validator.

## Baseline Validation

- `bun run lint`
- `bun run build`
- `bun run turbo:validate` for the local Turbo lint/build/test gate

## Repo Script Validation

- Codex skills and `AGENTS.md`: `bash scripts/validate_codex_skills.sh`
- Fast multi-check pass: `bash scripts/all_fast_validate_checks.sh`
- Dockerfile: `bash scripts/hadolint/validate_hadolint.sh`
- GitHub Actions local runner setup: `bash scripts/act/validate_act.sh`
- Swift build: `bash scripts/ios/swift-build.sh`
- Swift format: `ONLY_TOUCHED_FILES=false bash scripts/swiftformat/validate_swiftformat.sh`
- Swift lint: `ONLY_TOUCHED_FILES=false bash scripts/swiftlint/validate_swiftlint.sh`
- Other useful validators:
  - `bash scripts/validate-bun-test-timings.sh --run-unit-lane`, or pass an existing focused JUnit XML report to measure it directly
  - `bash scripts/detect-dead-code-ts.sh`

## Selection Rules

- TypeScript-only changes usually need `lint`, `build`, and relevant tests.
- Use `bun run turbo:*` scripts instead of bare `turbo ...`; Turbo is installed locally and may not be on the shell `PATH`.
- Shell or docs/config changes should prefer the matching script in `scripts/`.
- Android changes should use the Gradle wrapper from `android/`.
- iOS changes should use the existing `scripts/ios/` entry points.
- Write long validation output to `scratch/` and report only the actionable failures.

Versions

RepositoryScoreLicence
This page · kaeawc/auto-mobile90Apache-2.0
DiogoHSM/driver100MIT
boshu2/agentops100Apache-2.0
RemiPelloux/kill-my-idea100MIT
lalitmaganti/syntaqlite100Apache-2.0
zanderadam/engy100MIT
hirogakatageri/hirokata-claude-marketplace100MIT
fabricio21x/fbs100MIT
Kiran-980/1ml100MIT

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

  • 100validate-and-fix
    Run the full validation pipeline (make test-unit, make verify, make test-integration) and auto-fix trivial failures like black formatting, unused imports, and ruff-fixable lint errors. Use when the user asks to validate, run tests, check the pipeline, or verify changes are clean.
  • 100verification-engine
    Use when verifying build/test/lint before commit, PR, or completion claims. Runs verification pipeline in fresh subagent context with auto-repair. Triggers on /handoff-verify, pre-commit check, build verification, test validation.
  • 100verification-loop
    Use this skill for iterative verify-fix cycles across build, type, lint, test, and security gates until completion or explicit stop conditions.
  • 90check
    Validate code quality — auto-fix formatting/lint, verify types, run tests. Use when asked to "validate code", "check code", or validate before committing; also lint-only asks ("run linter", "fix lint errors"). Don't use for committing (/commit), pushing (/to-pr), or writing new tests (/tdd).
  • 84lint
    Lint and format checks across changed ecosystems without a full build, honoring each tool's config-file opt-in; --fix formats only, --code-fix applies semantic lint autofixes behind a confirmation gate. Use when: 'lint this', 'run the linter', 'format check', 'fix the…
  • 100run-tests
    Use this skill when the user asks to "run tests", "test this", "check if tests pass", "cargo test", "run clippy", "lint this", "check formatting", "cargo fmt", "CI checks", "verify changes", "does this pass tests", "run the full check", "pre-commit check", or wants to verify…

Feedback and reports

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