CtrlK
BlogDocsLog inGet started
Tessl Logo

peteski22/validate

Run all validators against recent code changes

50

Quality

63%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

Overview
Quality
Evals
Security
Files

contract.json

{
  "name": "validate",
  "version": "1.0.0",
  "input": ["git diff (all files)"],
  "output_schema": "aggregated hard/should/warn JSON from all validators",
  "assumes": [],
  "scope": [
    "Orchestrates all applicable validators based on detected file types",
    "Dispatches go-effective and go-proverbs for .go files",
    "Dispatches python-style for .py files",
    "Dispatches typescript-style for .ts/.tsx files",
    "Dispatches security for all files (exactly once)",
    "Dispatches state-machine for all files (exactly once)",
    "Dispatches error-handling for all files (exactly once)"
  ],
  "excludes": [
    "Direct validation logic (delegated to individual validators)",
    "Linting (deterministic checks run separately)"
  ],
  "hard_rules": [],
  "should_rules": [],
  "warn_rules": [],
  "references": [
    "go-effective",
    "go-proverbs",
    "python-style",
    "typescript-style",
    "security",
    "state-machine",
    "error-handling"
  ]
}

contract.json

SKILL.md

tile.json