skills.rest
thesimonho
thesimonhoCOMMUNITY
Explore all skills by this author →
Website𝕏@_SimonHoGitHub

verification

Run a five-phase build, type-check, lint, test, and console-audit workflow before PR submission.

26|Updated Apr 13, 2017
Search Tags:#testing#verification#code-quality#ci-cd#lint#build-check
One-click install
npx skills add https://github.com/thesimonho/dotfiles --skill verification-thesimonho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/thesimonho/dotfiles/tree/main/AI/skills/verification
Command: npx skills add https://github.com/thesimonho/dotfiles --skill verification-thesimonho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures a reliable, repeatable verification process before merging changes, reducing regressions and QA bottlenecks.

Core Features & Use Cases

  • Five-phase verification: Build, type-check, lint, test, and console audit gate changes before PR submission.
  • PR readiness reporting: Produces a clear readiness status and a summary of issues to fix.
  • Deterministic workflow: Runs checks in a fixed order to maintain consistency across PRs and releases.
  • Use Case: Before merging a feature branch, run the verification to catch build or test failures early.

Quick Start

Run the verification workflow on the current codebase to validate readiness for PR submission.

Frequently Asked Questions about verification

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

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

To verify code quality before a PR, you can run a structured workflow that sequentially executes build, type-check, lint, and test phases. This process catches regressions early and generates a final PR-readiness report.

What is a pre-merge verification workflow for feature branches?▼

A pre-merge verification workflow is a deterministic sequence of checks—build, type-check, lint, tests, and console audit—designed to ensure code quality. It maintains consistency across PRs by gating changes before submission.

How do I run build and lint checks before creating a PR?▼

You can run build and lint checks before creating a PR by triggering a verification workflow in either quick or full mode. The workflow runs these checks in a fixed order to identify and summarize issues to fix.

Can I audit console logs as part of my CI CD pipeline?▼

Yes, you can audit console logs as part of your CI CD pipeline through the console-audit phase. This phase is part of a five-step verification sequence that reviews logs to ensure PR readiness.

Does automated code verification work for refactoring workflows?▼

Yes, automated code verification works for refactoring workflows. It applies a deterministic sequence of build, type-check, lint, and test validations to catch regressions and reduce QA bottlenecks before merging.

Related Skills

Explore More Software Engineering Skills→
Vegetable-bird10086Vegetable-bird10086

building

Automate building the ExecuTorch AI framework from source for diverse platforms.

Community
Advanced
ibalasiteibalasite

land-and-deploy

Merge pull requests, wait for CI, and verify production health via canary checks.

Community
Advanced
Ramprasad4121Ramprasad4121
1

audit-prep-assistant

Prepare codebases for security review with static analysis and documentation.

Community
Advanced
krzemienskikrzemienski
2

build-quality-gates

Enforce sequential compile, lint, type-check, and bundle gates before deployment.

Community
Intermediate