Skip to content

/vt-c-finalize-check

Pre-merge verification using the finalization-orchestrator

Plugin: core-standards
Usage: /vt-c-finalize-check [--env staging|production] [--skip-audit] [--migration]


Finalize Check Command

Run pre-merge verification to ensure safe, compliant releases.

Usage

/vt-c-finalize-check                    # Standard finalization check
/vt-c-finalize-check --env production   # Specify target environment
/vt-c-finalize-check --migration        # Include migration safety checks
/vt-c-finalize-check --skip-audit       # Skip npm audit (not recommended)

What This Command Does

  1. Invokes the finalization-orchestrator to coordinate all pre-merge checks
  2. Runs dependency audit (npm audit) to check for vulnerabilities
  3. Runs final security scan via security-sentinel
  4. Checks migration safety (if --migration flag used) via data-integrity-guardian
  5. Verifies compliance against GDPR/SOC2 checklist
  6. Produces Go/No-Go decision with detailed report

Orchestration Flow

/vt-c-finalize-check
┌─────────────────────────────┐
│   finalization-orchestrator    │
└─────────────────────────────┘
      ├──▶ npm audit (parallel)
      ├──▶ security-sentinel (parallel)
      ├──▶ data-integrity-guardian (if migrations)
      └──▶ compliance-checklist skill
   Go/No-Go Report

Prerequisites

  • Implementation review completed (/vt-c-wf-review passed)
  • Code committed and pushed
  • Target environment specified

Output Format

## Finalization Readiness Report

### Target
- Environment: [staging/production]
- Branch: [branch name]
- Last commit: [commit hash]

### Checks

| Check | Status | Details |
|-------|--------|---------|
| npm audit | ✅/❌ | 0 critical, 0 high |
| Security scan | ✅/❌ | No vulnerabilities |
| Migration safety | ✅/❌/N/A | Migrations reviewed |
| Compliance | ✅/❌ | GDPR/SOC2 verified |

### Decision: GO / NO-GO

### Blocking Issues (if any)
[List of issues that must be resolved]

### Rollback Plan
[Documented rollback strategy]

Arguments

Flag Description
--env Target environment (staging, production)
--migration Include database migration safety checks
--skip-audit Skip npm audit (emergency use only)

When to Use

  • Before merging to main or releasing
  • After completing implementation review
  • When database migrations are involved
  • For compliance verification before release

Next Steps After Finalize-Check

If GO: 1. Merge PR to main 2. Monitor post-merge metrics 3. Verify feature functionality

If NO-GO: 1. Review blocking issues 2. Fix issues 3. Re-run /vt-c-finalize-check 4. Obtain new GO decision