validate

Run linting and tests for Swift and Python before committing.

6|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/UnaMentis/unamentis --skill validate-unamentis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/UnaMentis/unamentis/tree/main/.claude/skills/validate
Command: npx skills add https://github.com/UnaMentis/unamentis --skill validate-unamentis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill enforces the Definition of Done by running lint checks and tests before work is considered complete, ensuring code quality and reliability.

Core Features & Use Cases

  • Lint checks (SwiftLint strict mode) must pass before code is accepted.
  • Python lint checks (ruff) and security scans (bandit) run as part of the workflow.
  • Tests (unit and integration) run, with an optional full suite and coverage threshold when requested.

Quick Start

Run the validate command to perform linting and tests before committing changes.

Frequently Asked Questions about validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pre-commit checks for Swift and Python projects?

Automate pre-commit checks by running a validation script that enforces linting and tests pass before code is committed. This workflow applies SwiftLint strict mode and ruff to ensure code quality and reliability across Swift and Python projects.

What is included in a pre-commit validation workflow for code quality?

A pre-commit validation workflow includes static analysis, security scans, and unit and integration tests. It runs Python lint checks with ruff, security scans with bandit, and SwiftLint strict mode to enforce the Definition of Done before code is accepted.

Do I need SwiftLint and ruff installed to run pre-commit lint checks?

Yes, you need SwiftLint and ruff installed to run pre-commit lint checks. The validation workflow requires these specific tools, along with your test scripts, to execute static analysis and report a clear PASS or FAIL verdict before committing code.

Can I run a full test suite with coverage thresholds during pre-commit validation?

Yes, you can run a full test suite with coverage thresholds during pre-commit validation. Unit and integration tests run automatically, and you can request the full suite and coverage threshold enforcement to ensure comprehensive testing before code is committed.

Why does my pre-commit validation report a FAIL verdict?

Pre-commit validation reports a FAIL verdict when lint checks, security scans, or tests do not pass. Strict mode SwiftLint, ruff linting, bandit security scans, or test script failures will block the commit and prevent code from being accepted until issues are resolved.