skills.rest
ovisan
ovisanCOMMUNITY
Explore all skills by this author →
GitHub

verification-loop

Runs build, type, lint, test, security, and diff checks to produce a verification report.

2|Updated Mar 29, 2015
Search Tags:#code quality#testing#pull request#verification#security scan#lint#type check
One-click install
npx skills add https://github.com/ovisan/dotfiles --skill verification-loop-ovisan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/ovisan/dotfiles/tree/main/.agents/skills/verification-loop
Command: npx skills add https://github.com/ovisan/dotfiles --skill verification-loop-ovisan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often ship with hidden build failures, type errors, lint warnings, failing tests, or leaked secrets. This Skill runs a structured multi-phase verification pass before you create a PR, catching quality issues early. ## Core Features & Use Cases - Six-Phase Verification: Sequentially checks build, TypeScript/Python types, lint, test coverage, security patterns (secrets, console.log), and git diff review. - Standardized Report: Produces a PASS/FAIL summary with test counts, coverage percentage, and a READY/NOT READY verdict for PRs. - Use Case: After refactoring a TypeScript feature, invoke the skill to run tsc, eslint, and the test suite, then receive a consolidated report listing the two type errors and one leaked API key pattern to fix before opening your PR. ## Quick Start Ask the assistant to run the verification loop on the current project and report whether the changes are ready for a PR.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I verify code quality before creating a pull request?▼

Run a verification loop that checks build success, type errors, lint warnings, test results with coverage, and security patterns. The skill executes each phase via shell commands and outputs a READY or NOT READY verdict with issues to fix.

What checks should I run after refactoring TypeScript code?▼

Run the build, then tsc --noEmit for type errors, your lint script, and the test suite with coverage. Finish by reviewing git diff output for unintended changes, missing error handling, and edge cases.

Does this verification workflow support Python projects?▼

Yes, the skill includes Python-specific commands: pyright for type checking and ruff for linting. JavaScript and TypeScript projects use npm or pnpm build, tsc, and npm run lint instead.

How do I check for leaked secrets in source code?▼

Use grep to scan source files for patterns like sk- prefixes and api_key strings. The skill also flags leftover console.log statements in TypeScript source directories as part of its security phase.

What test coverage threshold does the verification require?▼

The skill targets a minimum of 80 percent coverage, reported alongside total, passed, and failed test counts. Projects below the threshold are flagged in the final verification report.

Related Skills

Explore More Software Engineering Skills→
devbasexdevbasex
1

refactoring

Restructure code without changing behavior using test-guarded incremental refactoring steps.

Official
Advanced
taracodlabstaracodlabs
799

github-pr-workflow

Manages the full GitHub pull request lifecycle using the gh CLI.

Official
Intermediate
llmh333llmh333

plankton-code-quality

Format and lint edited files via PostToolUse hooks with LLM-based remediation.

Community
Advanced
thermiteauthermiteau

ci-integration

Run lint, typecheck, and tests locally before pushing and monitor GitHub Actions results.

Official
Intermediate