gxpm-verify

Orchestrate local verification runs and collect step evidence for gxpm transitions.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/laozhong86/gxpm --skill gxpm-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gxpm-verify
Source: https://github.com/laozhong86/gxpm/tree/main/skills/gxpm-verify
Command: npx skills add https://github.com/laozhong86/gxpm --skill gxpm-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local verification is critical before progressing issues; this skill orchestrates the verification pipeline and records per-step evidence to ensure auditable transitions within the gxpm workflow.

Core Features & Use Cases

  • Orchestrates end-to-end local verification and evidence collection before phase transitions.
  • Validates completion of required artifacts (local-verify) and stores step results for audit.
  • Use Case: When an implement-to-local-verify transition is triggered, this skill runs a predefined verification sequence and collects per-step outcomes to guarantee a reproducible, auditable pipeline.

Quick Start

Trigger the local verification pipeline after transitioning from implement to local-verify to collect all step-by-step evidence.

Frequently Asked Questions about gxpm-verify

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

FAQPage Schema
How do I capture local verification evidence for workflow stage transitions?

Local verification evidence is captured by running a predefined verification sequence and recording step results, exit codes, durations, and summaries in a local-verify artifact to ensure auditable stage transitions.

What is a local-verify artifact and when do I need it?

A local-verify artifact is a required record for stage transitions in gxpm workflows, containing per-step verification outcomes, exit codes, and durations to guarantee a reproducible and auditable pipeline.

How do I run a full verification pipeline for an issue?

Run a full verification pipeline by triggering the skill after an implement-to-local-verify transition, which orchestrates the end-to-end sequence and collects per-step evidence to ensure artifacts are complete before ac-check.

Does the verification pipeline validate artifact completion before ac-check?

Yes, the verification pipeline validates the completion of required artifacts and confirms eligibility before proceeding to ac-check, ensuring all local-verify evidence is complete and auditable.

What step details are stored when collecting evidence for local verification?

Evidence collection stores per-step outcomes including exit codes, durations, and summaries within the local-verify artifact, providing an auditable record of the verification pipeline execution.

Why does local verification require capturing exit codes and durations?

Capturing exit codes and durations is required to secure safe stage transitions and provide reproducible, auditable evidence that all verification steps completed successfully before progressing the workflow.