How do I install the Pmtl Verify Quality Gate skill?

Run npx skillmds add majiayu000/pmtl-verify-quality-gate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pmtl Verify Quality Gate safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pmtl Verify Quality Gate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pmtl Verify Quality Gate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pmtl Verify Quality Gate?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pmtl Verify Quality Gate by majiayu000

Name: Pmtl Verify Quality Gate
Rating: 4.5 (4 reviews)
Author: majiayu000

Pmtl Verify Quality Gate

PMTL_VN verification skill for code quality gates. Use after meaningful changes to run the strongest relevant checks, usually targeted tests, typecheck, lint, and build-oriented validation, instead of relying on manual confidence.

majiayu000 c738363 2 files · 3.3 KB Updated Sep 9, 2026 567 repo stars

File contents

PMTL Verify Quality Gate

Purpose

Run the strongest relevant checks after implementation so delivery is backed by evidence instead of confidence.

Use When

Any meaningful code change is considered done.
You need a deterministic verification path for web, CMS, or repo-wide edits.

Required Inputs

touched scope: web, cms, or all
whether tests may be skipped for a narrowly justified reason
whether narrower domain verifiers are also required

Expected Output

Command results that show what passed, what failed, and which runtime was used.

Default order

Targeted tests for touched areas.
Typecheck for the affected package or the monorepo.
Lint for the affected package or the monorepo.
Build or smoke verification when contracts changed.

Execution Approach

Choose the narrowest scope that still proves the change.
Run the quality gate through the repo wrapper instead of ad hoc commands.
Escalate to smoke or domain-specific verification when contracts changed.

Script

Primary entrypoint: py infra/tools/codex_actions.py quality-gate ...

Compatibility wrapper: scripts/run_quality_gate.py

Example:

py infra/tools/codex_actions.py quality-gate --scope all
py infra/tools/codex_actions.py quality-gate --scope web --skip-tests

Verification

Treat non-zero exit codes as a failed gate.
Include the real command output summary in the final report, not only "tests passed".

Quality Criteria

Verification scope is as narrow as possible without becoming misleading.
Final reporting includes the actual executed scope and runtime.
Quality gate is not used as a substitute for auth/search/domain-specific verification when those lanes changed.

Edge Cases

Legacy cms naming still exists in the helper even though forward architecture is apps/api; call that out plainly when relevant.
A passing quality gate does not prove runtime health, auth correctness, or search freshness by itself.
Local environment issues can break a gate independently of the code change; distinguish infra failure from code failure.

References

infra/tools/codex_actions.py
scripts/run_quality_gate.py

---name: pmtl-verify-quality-gatedescription: PMTL_VN verification skill for code quality gates. Use after meaningful changes to run the strongest relevant checks, usually targeted tests, typecheck, lint, and build-oriented validation, instead of relying on manual confidence.--- # PMTL Verify Quality Gate ## Purpose Run the strongest relevant checks after implementation so delivery is backed by evidence instead of confidence. ## Use When - Any meaningful code change is considered done. - You need a deterministic verification path for web, CMS, or repo-wide edits. ## Required Inputs - touched scope: `web`, `cms`, or `all` - whether tests may be skipped for a narrowly justified reason - whether narrower domain verifiers are also required ## Expected Output - Command results that show what passed, what failed, and which runtime was used. ## Default order 1. Targeted tests for touched areas. 2. Typecheck for the affected package or the monorepo. 3. Lint for the affected package or the monorepo. 4. Build or smoke verification when contracts changed. ## Execution Approach 1. Choose the narrowest scope that still proves the change. 2. Run the quality gate through the repo wrapper instead of ad hoc commands. 3. Escalate to smoke or domain-specific verification when contracts changed. ## Script Primary entrypoint: `py infra/tools/codex_actions.py quality-gate ...` Compatibility wrapper: `scripts/run_quality_gate.py` Example: ```bash py infra/tools/codex_actions.py quality-gate --scope all py infra/tools/codex_actions.py quality-gate --scope web --skip-tests ``` ## Verification - Treat non-zero exit codes as a failed gate. - Include the real command output summary in the final report, not only "tests passed". ## Quality Criteria - Verification scope is as narrow as possible without becoming misleading. - Final reporting includes the actual executed scope and runtime. - Quality gate is not used as a substitute for auth/search/domain-specific verification when those lanes changed. ## Edge Cases - Legacy `cms` naming still exists in the helper even though forward architecture is `apps/api`; call that out plainly when relevant. - A passing quality gate does not prove runtime health, auth correctness, or search freshness by itself. - Local environment issues can break a gate independently of the code change; distinguish infra failure from code failure. ## References - `infra/tools/codex_actions.py` - `scripts/run_quality_gate.py`

Frequently asked questions