certify

Runs tests, type checks, lint, and build to produce evidence for PR readiness.

12|Updated Apr 17, 2026

Search Tags:#build #evidence #verify #lint #ci #tests #type-check

Ready to run

npx skills add https://github.com/Alexander-Tyagunov/magician --skill certify-alexander-tyagunov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: certify
Source: https://github.com/Alexander-Tyagunov/magician/tree/main/skills/certify
Command: npx skills add https://github.com/Alexander-Tyagunov/magician --skill certify-alexander-tyagunov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies code quality by running tests, type checks, lint, and build, and collecting evidence before PRs to reduce regressions and release risks.

Core Features & Use Cases

Sequential verification across tests, type checks, lint, and builds
Evidence collection and a ready-to-attach report for PRs
Works across multi-language stacks and CI workflows

Quick Start

Run the full verification loop locally or in CI to ensure all checks pass before creating a PR.

Frequently Asked Questions about certify

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

FAQPage Schema

How do I automate code verification for tests, type checks, and lint before creating a PR?▼

Automate code verification by running a sequential loop of tests, type checks, and lint across your multi-language codebase to enforce a passing state before integration. This process reduces regressions and release risks.

What is the best way to collect evidence for PR readiness in a CI workflow?▼

Collect evidence for PR readiness by executing builds and verification checks, then generating a ready-to-attach report. This ensures high-trust releases by satisfying essential evidence-generation requirements.

Can I enforce full verification across multi-language stacks and CI workflows?▼

Yes, full verification applies across multi-language stacks and CI workflows. It sequentially executes tests, type checks, lint, and builds to guarantee code passes all essential checks before integration.

Why run type checks and lint sequentially with tests before a pull request?▼

Running type checks, lint, and tests sequentially before a pull request verifies code quality and catches errors early. This end-to-end verification reduces regressions and ensures a stable, high-trust release.

Does pre-PR verification work without specific CI pipeline dependencies?▼

Yes, pre-PR verification works without specific dependencies. You can run the full verification loop locally or integrate it directly into your existing CI workflows to ensure all checks pass.

What are the limitations of enforcing full verification before PRs?▼

Limitations include the time cost of running sequential tests, type checks, lint, and builds across large multi-language codebases. However, this end-to-end process is necessary to guarantee a passing state before integration.