verify

Run lint, type-check, and test commands to produce a SHIP or HOLD verdict.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/chughtapan/safer-by-default --skill verify-chughtapan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/chughtapan/safer-by-default/tree/main/skills/verify
Command: npx skills add https://github.com/chughtapan/safer-by-default --skill verify-chughtapan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the PR verification gate by running lint, tests, and type checks and comparing results against acceptance criteria to determine if a PR should be shipped or held.

Core Features & Use Cases

  • Command discovery: Detect lint, type-check, and test commands from common project configs (package.json, pyproject.toml, Cargo.toml, Makefile, CI configs) and run them.
  • Verdict generation: Collect command outputs and exit codes to produce a reliable SHIP/HOLD decision.
  • Acceptance criteria alignment: Read sub-issue criteria and PR diff to publish a formal verdict on the PR and mirror it to the sub-issue.
  • Automation and routing: Transition labels and route follow-up work based on the verdict, without modifying source files.

Quick Start

Provide the PR number and let the system detect and run the checks, then publish the verdict and update the sub-issue.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate pull-request verification for lint, type-check, and test commands?

Automated pull-request verification detects lint, type-check, and test commands from project configs like package.json and pyproject.toml, runs them against the PR head, and publishes a SHIP or HOLD verdict artifact.

How does a merge gate align CI test results with acceptance criteria?

A merge gate aligns CI test results with acceptance criteria by reading sub-issue requirements and the PR diff, then comparing command outputs to decide whether to ship, hold, or ship with concerns.

Can I gate PRs without modifying source files?

You can gate PRs without modifying source files because the verification process only runs checks, generates a verifiable verdict artifact on the PR, and mirrors it to the sub-issue.

How do I discover lint and test commands from common project configurations?

Discover lint and test commands by parsing common project configuration files such as Cargo.toml, Makefile, package.json, pyproject.toml, and CI configs to automatically identify and run the correct checks.

What is the difference between SHIP, HOLD, and SHIP_WITH_CONCERNS verdicts?

SHIP, HOLD, and SHIP_WITH_CONCERNS are verdicts determined by comparing lint, type-check, and test command exit codes against sub-issue acceptance criteria and the PR diff.

Does PR verification support Python and Rust project configs?

PR verification supports Python and Rust projects by detecting commands from pyproject.toml and Cargo.toml, running the checks, and routing follow-up work based on the verdict.