Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/pmtl-verify-quality-gate
SKILL.md
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, orall - 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
cmsnaming still exists in the helper even though forward architecture isapps/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.pyscripts/run_quality_gate.py
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?