skills.rest
Kimjiman
KimjimanCOMMUNITY
Explore all skills by this author →
GitHub

verification-loop

Run build, type, lint, test, security, and diff checks before pull requests.

Updated May 24, 2023
Search Tags:#code quality#testing#ci/cd#linting#verification#security scan
One-click install
npx skills add https://github.com/Kimjiman/basic-arch --skill verification-loop-kimjiman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/Kimjiman/basic-arch/tree/main/.claude/skills/verification-loop
Command: npx skills add https://github.com/Kimjiman/basic-arch --skill verification-loop-kimjiman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of verifying code quality, build status, test coverage, and security vulnerabilities, ensuring that code meets predefined standards before being submitted for review.

Core Features & Use Cases

  • Build Verification: Checks if the project compiles successfully.
  • Type Checking: Validates TypeScript or Python type correctness.
  • Linting: Enforces code style and identifies potential issues.
  • Test Suite Execution: Runs tests and reports coverage.
  • Security Scan: Detects secrets and excessive logging.
  • Diff Review: Highlights code changes for manual inspection.
  • Use Case: Before creating a Pull Request for a new feature, run this skill to catch any build errors, type mismatches, failing tests, or accidental secret leaks, ensuring a smoother review process.

Quick Start

Run the verification loop to check the current codebase.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I run code quality checks and security scans before creating a PR?▼

To run code quality checks before a PR, execute a comprehensive verification loop covering build status, type checking, linting, test coverage, and secret detection to enforce quality gates on code changes.

What is included in a pre-submission code verification process?▼

A pre-submission code verification process includes build compilation checks, TypeScript or Python type validation, linting, test suite execution with coverage, security scanning for leaked secrets, and a diff review of changes.

Can I use automated verification to check for leaked secrets and excessive logging in my codebase?▼

Yes, automated verification can check for leaked secrets and excessive logging. The security scan phase evaluates your codebase to detect hard-coded secrets and inappropriate log output before submission.

Does the verification process support both TypeScript and Python type checking?▼

Yes, the verification process supports both TypeScript and Python type checking. It validates type correctness automatically during the execution phase to catch mismatches before code review.

What's the best way to enforce quality gates and review code diffs before submission?▼

The best way to enforce quality gates and review code diffs is running a multi-phase verification script that compiles the build, runs tests with coverage, scans for vulnerabilities, and highlights code changes for manual inspection.

Related Skills

Explore More Software Engineering Skills→
WanxiaJaneYangWanxiaJaneYang

repo-standards

Validate code formatting, linting, type-checking, and tests for pull requests.

Community
Basic
thanh-abaiithanh-abaii
34

gs:land-and-deploy

Merge pull requests, run CI/CD pipelines, and verify production health.

Community
Advanced
0xRayAI0xRayAI

lint

Run node-based linting servers to enforce code quality standards.

Official
Intermediate
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced