New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Lean Verification

by epam in epam/ai-dial-chat

Run build/lint/test/typecheck verification during implementation or before merge while minimizing token spend.

Apache-2.0Auto-check passedTesting & QA

Install Lean Verification

skills CLI
$ npx skills add epam/ai-dial-chat --skill lean-verification -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install epam/ai-dial-chat lean-verification --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/epam/ai-dial-chat.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/lean-verification .claude/skills/lean-verification && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lean-verification
GitHub stars
504
Token cost
~563 tokens
SKILL.md length
249 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run build/lint/test/typecheck verification during implementation or before merge while minimizing token spend.

  • Tasks that involve Unit testing
  • SKILL.md covers Verification tiers, Verification cadence and Failure handling
  • Calls npm
  • Tasks that involve Linting and formatting

What it does

Lean Verification is an agent skill from epam/ai-dial-chat. Run build/lint/test/typecheck verification during implementation or before merge while minimizing token spend. Use instead of raw Nx or Vitest commands, especially during an OpenSpec task slice.

Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Unit testing and Linting and formatting. It works with Vitest. The repository describes itself as: A default UI for AI DIAL. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Unit testing
  • Tasks that involve Linting and formatting

Example prompts

  • “/lean-verification”

What it can do on your machine

Read from SKILL.md and the folder at commit 2d66a8d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lean Verification loads about 563 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 249 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~563

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from epam/ai-dial-chat at commit 2d66a8d, republished under its Apache-2.0 licence (© epam). 249 words, ~563 tokens.

Download SKILL.mdSave it as .claude/skills/lean-verification/SKILL.md (or your agent's skills folder).
name
lean-verification
description
Run build/lint/test/typecheck verification during implementation or before merge while minimizing token spend. Use instead of raw Nx or Vitest commands, especially during an OpenSpec task slice.

Lean verification

Use the narrowest verification tier that can disprove the current change. The scripts capture full output under tmp/agent-logs/; successful runs return a two-line status, while failures return a bounded excerpt and the log path.

Verification tiers

bash
# Red/green loop: pass one or more workspace-relative test paths.
npm run test:file -- libs/example/src/Foo.spec.ts

# Completed task or vertical slice: affected projects only.
npm run verify:changed

# Final pre-merge gate: full, non-mutating verification.
npm run verify:full
  • test:file is the default during implementation. It groups paths by their nearest Vite/Vitest config and runs only those files.
  • test:changed and verify:changed use Nx's affected project graph with origin/development as the base.
  • verify:affected remains available as an explicit affected verification alias.
  • verify:full uses lint:check, never the mutating npm run lint command.
  • build:quiet builds affected projects when the change can affect bundling.

This workspace contains many Nx projects, so affected verification narrows typecheck, lint, test, and build work to the changed projects and their affected dependents. Prefer exact tests for the mid-task loop; reserve project-level affected checks for a completed slice. A successful affected run may execute no task when only docs or agent configuration changed, so it is not a substitute for the final full gate.

Verification cadence

Batch related edits for one task-list item before re-verifying. Do not rerun a suite after each individual edit. OpenSpec tasks should name their exact test files so the red/green loop does not require rediscovery.

Failure handling

Use the printed failure excerpt first. Search or read only the relevant portion of the saved log if that excerpt is insufficient; do not load the whole log or rerun with a verbose reporter by default. Keep --reporter=minimal so passing test logs do not enter the conversation.

© epam, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/lean-verification of epam/ai-dial-chat.

Open the folder on GitHubat commit 2d66a8d

Compare with similar skills

Lean Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lean Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lean Verification this skillepam/ai-dial-chat504—~563Automated safety check: PassApache-2.0
Ha Frontend Testinghome-assistant/frontend5.7k—~1.7kAutomated safety check: PassApache-2.0
Eslint Vitest Rule Testerantfu-collective/eslint-vitest-rule-tester142—~1.3kAutomated safety check: PassMIT
Run Testsartcc/freelingo160—~976Automated safety check: PassAGPL-3.0
Kc Preflightimran31415/kube-coder388—~1kAutomated safety check: NotesMIT
Validatejuliepy/AI-Engineer-from-scrach433—~500Automated safety check: PassNone

Similar skills

  • Ha Frontend Testing

    home-assistant/frontend

    Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.

    5.7k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Eslint Vitest Rule Tester

    antfu-collective/eslint-vitest-rule-tester

    Help users test ESLint rules with Vitest, supporting snapshot testing and custom assertions

    142 GitHub stars~1.3k tokensUpdated 28 days ago
    Testing & QAAuto-check passed

  • Run Tests

    artcc/freelingo

    A skill your agent uses when the user asks to run tests, ejecutar tests, lanzar tests, pytest, vitest, check types, typecheck, lint, or verify the codebase.

    160 GitHub stars~976 tokensUpdated today
    Testing & QAAuto-check passed

  • Kc Preflight

    imran31415/kube-coder

    Run kube-coder's full CI suite locally before pushing — helm lint + unit tests, server.py tests, dashboard + controller SPA builds + vitest, and shell syntax checks.

    388 GitHub stars~1k tokensUpdated today
    Testing & QAAuto-check: notes

  • Validate

    juliepy/AI-Engineer-from-scrach

    Run the full quality gate (ruff + mypy + pytest + tsc + vitest) and report PASS/FAIL for each command.

    433 GitHub stars~500 tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Typescript Testing

    ComposioHQ/composio

    Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests.

    30k GitHub stars~222 tokensUpdated today
    Testing & QAAuto-check passed

More from epam/ai-dial-chat

All 18 skills in this repo

  • Refactoring Audit

    epam/ai-dial-chat

    Deep codebase refactoring audit for AI DIAL Chat. An agent skill from epam/ai-dial-chat.

    504 GitHub stars~4.3k tokensUpdated today
    Auto-check passed

  • Address Current Branch Review

    epam/ai-dial-chat

    Read unresolved GitHub code review threads for the pull request associated with the current branch, classify each comment, and implement and verify required code fixes.

    504 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Create Ticket

    epam/ai-dial-chat

    Interactively create OR update GitHub issues (Bug, Feature, Task) for the current repository.

    504 GitHub stars~4.6k tokensUpdated today
    Auto-check passed

  • Dep Scan

    epam/ai-dial-chat

    Runs Trivy filesystem scan against the repo root and emits structured vulnerability findings (CVE, package, versions) in the SDLC reviewer schema.

    504 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Figma

    epam/ai-dial-chat

    Design-to-code workflow for Figma designs. An agent skill from epam/ai-dial-chat.

    504 GitHub stars~997 tokensUpdated today
    Auto-check passed

  • Git Ship

    epam/ai-dial-chat

    A skill your agent uses whenever the user wants to commit, push, or ship changes in a git repository.

    504 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Lean Verification

What does Lean Verification do?

Run build/lint/test/typecheck verification during implementation or before merge while minimizing token spend. Lean Verification is an agent skill from epam/ai-dial-chat. Run build/lint/test/typecheck verification during implementation or before merge while minimizing token spend.

When should I use Lean Verification?

Lean Verification fits situations like: tasks that involve Unit testing; tasks that involve Linting and formatting.

How do I install Lean Verification in Claude Code?

Run `npx skills add epam/ai-dial-chat --skill lean-verification -a claude-code`. Or copy the skill folder (.claude/skills/lean-verification in epam/ai-dial-chat) into .claude/skills/lean-verification in your project. Claude Code loads it when a task matches its description.

How do I install Lean Verification in Codex?

Run `npx skills add epam/ai-dial-chat --skill lean-verification -a codex`. Or copy the skill folder (.claude/skills/lean-verification in epam/ai-dial-chat) into .agents/skills/lean-verification in your project. Codex loads it when a task matches its description.

Can I use Lean Verification in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add epam/ai-dial-chat --skill lean-verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lean-verification, .gemini/skills/lean-verification, .github/skills/lean-verification and .opencode/skills/lean-verification in your project.

What does Lean Verification need to run?

Going by SKILL.md and its folder, Lean Verification needs the command-line tools its instructions call (npm).

Does Lean Verification access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Lean Verification safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lean Verification use?

Lean Verification is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lean Verification use?

About 563 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Lean Verification?

Skills that share tags, products or a category with Lean Verification: Ha Frontend Testing (home-assistant/frontend, 5.7k stars), Eslint Vitest Rule Tester (antfu-collective/eslint-vitest-rule-tester, 142 stars), Run Tests (artcc/freelingo, 160 stars) and Kc Preflight (imran31415/kube-coder, 388 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lean Verification?

epam (a GitHub organization) maintains it in epam/ai-dial-chat, which has 504 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: epam/ai-dial-chat on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.